StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. Oracle vs VoltDB

Oracle vs VoltDB

OverviewDecisionsComparisonAlternatives

Overview

Oracle
Oracle
Stacks2.6K
Followers1.8K
Votes113
VoltDB
VoltDB
Stacks18
Followers72
Votes18

Oracle vs VoltDB: What are the differences?

## Key Differences between Oracle and VoltDB

Oracle and VoltDB are both widely used database management systems, but they differ in several key aspects. Here are the main differences between the two:

1. **Architecture**: One major difference between Oracle and VoltDB is their architecture. Oracle follows a traditional disk-based architecture, where data is stored on disk and accessed when needed. In contrast, VoltDB uses an in-memory architecture, keeping all data in RAM for faster processing.
   
2. **Scalability**: Another significant difference is scalability. Oracle can scale vertically by adding more resources to a single server, while VoltDB is designed for horizontal scalability, allowing additional servers to be added to distribute the workload.
   
3. **Consistency**: Oracle utilizes a strong consistency model, ensuring that all data reads reflect the latest updates. VoltDB, on the other hand, implements an ACID-compliant distributed in-memory database, providing predictable and consistent performance even in distributed environments.
   
4. **Performance**: In terms of performance, VoltDB is known for its high throughput and low latency, ideal for real-time applications that require fast data processing. While Oracle also offers excellent performance, VoltDB's in-memory architecture gives it an edge in certain use cases.
   
5. **Ease of Use**: Oracle is a comprehensive database system with a wide range of features and functionalities, which can make it complex to manage. VoltDB, on the other hand, is known for its simplicity and ease of use, making it a preferred choice for developers looking for a streamlined solution.
   
6. **Use Cases**: Oracle is often used for traditional enterprise applications that require complex queries and support for various data types. VoltDB, on the other hand, is well-suited for real-time analytics, IoT applications, and other use cases that demand high-speed data processing.

In Summary, while Oracle is a robust and established database system suitable for a wide range of applications, VoltDB stands out for its in-memory architecture, scalability, and performance in real-time processing environments.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Oracle, VoltDB

Daniel
Daniel

Data Engineer at Dimensigon

Jul 18, 2020

Decided

We have chosen Tibero over Oracle because we want to offer a PL/SQL-as-a-Service that the users can deploy in any Cloud without concerns from our website at some standard cost. With Oracle Database, developers would have to worry about what they implement and the related costs of each feature but the licensing model from Tibero is just 1 price and we have all features included, so we don't have to worry and developers using our SQLaaS neither. PostgreSQL would be open source. We have chosen Tibero over Oracle because we want to offer a PL/SQL that you can deploy in any Cloud without concerns. PostgreSQL would be the open source option but we need to offer an SQLaaS with encryption and more enterprise features in the background and best value option we have found, it was Tibero Database for PL/SQL-based applications.

496k views496k
Comments
Abigail
Abigail

Dec 6, 2019

Decided

In the field of bioinformatics, we regularly work with hierarchical and unstructured document data. Unstructured text data from PDFs, image data from radiographs, phylogenetic trees and cladograms, network graphs, streaming ECG data... none of it fits into a traditional SQL database particularly well. As such, we prefer to use document oriented databases.

MongoDB is probably the oldest component in our stack besides Javascript, having been in it for over 5 years. At the time, we were looking for a technology that could simply cache our data visualization state (stored in JSON) in a database as-is without any destructive normalization. MongoDB was the perfect tool; and has been exceeding expectations ever since.

Trivia fact: some of the earliest electronic medical records (EMRs) used a document oriented database called MUMPS as early as the 1960s, prior to the invention of SQL. MUMPS is still in use today in systems like Epic and VistA, and stores upwards of 40% of all medical records at hospitals. So, we saw MongoDB as something as a 21st century version of the MUMPS database.

540k views540k
Comments
Abigail
Abigail

Dec 10, 2019

Decided

We wanted a JSON datastore that could save the state of our bioinformatics visualizations without destructive normalization. As a leading NoSQL data storage technology, MongoDB has been a perfect fit for our needs. Plus it's open source, and has an enterprise SLA scale-out path, with support of hosted solutions like Atlas. Mongo has been an absolute champ. So much so that SQL and Oracle have begun shipping JSON column types as a new feature for their databases. And when Fast Healthcare Interoperability Resources (FHIR) announced support for JSON, we basically had our FHIR datalake technology.

558k views558k
Comments

Detailed Comparison

Oracle
Oracle
VoltDB
VoltDB

Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.

VoltDB is a fundamental redesign of the RDBMS that provides unparalleled performance and scalability on bare-metal, virtualized and cloud infrastructures. VoltDB is a modern in-memory architecture that supports both SQL + Java with data durability and fault tolerance.

-
In-Memory Performance with On-Disk Durability;Transparent Scalability with Data Consistency;NewSQL – All the benefits of SQL with Unlimited Scalability;JSON Support for Agile Development;ACID Compliant Transactions;Export Data to OLAP Stores and Data Warehouses
Statistics
Stacks
2.6K
Stacks
18
Followers
1.8K
Followers
72
Votes
113
Votes
18
Pros & Cons
Pros
  • 44
    Reliable
  • 33
    Enterprise
  • 15
    High Availability
  • 5
    Hard to maintain
  • 5
    Expensive
Cons
  • 14
    Expensive
Pros
  • 5
    SQL + Java
  • 4
    In-memory database
  • 4
    A brainchild of Michael Stonebraker
  • 3
    Very Fast
  • 2
    NewSQL

What are some alternatives to Oracle, VoltDB?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

Redis

Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase