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. MySQL vs VoltDB

MySQL vs VoltDB

OverviewDecisionsComparisonAlternatives

Overview

MySQL
MySQL
Stacks129.6K
Followers108.6K
Votes3.8K
GitHub Stars11.8K
Forks4.1K
VoltDB
VoltDB
Stacks18
Followers72
Votes18

MySQL vs VoltDB: What are the differences?

MySQL vs VoltDB

MySQL and VoltDB are both database management systems, but they differ in various aspects. Here are the key differences between MySQL and VoltDB:

  1. Architecture: MySQL follows a traditional client-server architecture, where multiple clients can connect to a central database server. On the other hand, VoltDB utilizes a distributed shared-nothing architecture, where data is partitioned across multiple servers, enabling higher scalability and performance for certain workloads.

  2. ACID Compliance: Both MySQL and VoltDB support ACID (Atomicity, Consistency, Isolation, Durability) properties, ensuring transactional integrity. However, VoltDB places a stronger emphasis on performance and offers an in-memory, fully parallelized execution engine that can process high volumes of transactions with minimal latency, making it suitable for real-time applications.

  3. Data Replication: MySQL offers various options for data replication, such as Master-Slave replication and Group Replication, allowing for data redundancy and high availability. In contrast, VoltDB does not natively support data replication across multiple nodes. Instead, it focuses on maintaining consistency through its distributed architecture and integrated replication within individual partitions.

  4. Data Model: MySQL is a relational database management system (RDBMS) that supports a structured data model with tables, rows, and columns. It provides SQL as the query language for data manipulation. VoltDB, on the other hand, has a hybrid data model that combines relational and object-oriented principles. It uses SQL for querying and updates, but also provides an integrated procedural language (VoltDB SQL) for complex real-time analytics and application logic.

  5. Scale-Out Capabilities: MySQL supports horizontal scale-out through techniques like sharding and replication, allowing for distributed storage across multiple servers. VoltDB, however, is specifically designed for scale-out scenarios, automatically distributing data and processing across multiple nodes and exploiting parallelism to handle high transaction volumes.

  6. Fault Tolerance: MySQL achieves fault tolerance through replication and failover mechanisms. If a primary server fails, another server can take over to ensure continuous availability. In VoltDB, fault tolerance is built into its distributed architecture. It maintains multiple replicas of data partitions, enabling automatic failover without relying on external replication mechanisms.

In summary, MySQL is a versatile RDBMS that offers a wide range of features for traditional data storage and processing, while VoltDB is a specialized in-memory database designed for high-speed, real-time transaction processing. VoltDB's distributed architecture and parallel execution engine make it well-suited for applications requiring extreme performance and scalability.

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 MySQL, VoltDB

Kyle
Kyle

Web Application Developer at Redacted DevWorks

Dec 3, 2019

DecidedonPostGISPostGIS

While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.

MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.

It was very disappointing.

I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.

I was very disappointed.

Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.

449k views449k
Comments
Ido
Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k
Comments
Navraj
Navraj

CEO at SuPragma

Apr 16, 2020

Needs adviceonMySQLMySQLPostgreSQLPostgreSQL

I asked my last question incorrectly. Rephrasing it here.

I am looking for the most secure open source database for my project I'm starting: https://github.com/SuPragma/SuPragma/wiki

Which database is more secure? MySQL or PostgreSQL? Are there others I should be considering? Is it possible to change the encryption keys dynamically?

Thanks,

Raj

401k views401k
Comments

Detailed Comparison

MySQL
MySQL
VoltDB
VoltDB

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.

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
GitHub Stars
11.8K
GitHub Stars
-
GitHub Forks
4.1K
GitHub Forks
-
Stacks
129.6K
Stacks
18
Followers
108.6K
Followers
72
Votes
3.8K
Votes
18
Pros & Cons
Pros
  • 800
    Sql
  • 679
    Free
  • 562
    Easy
  • 528
    Widely used
  • 490
    Open source
Cons
  • 16
    Owned by a company with their own agenda
  • 3
    Can't roll back schema changes
Pros
  • 5
    SQL + Java
  • 4
    In-memory database
  • 4
    A brainchild of Michael Stonebraker
  • 3
    Very Fast
  • 2
    NewSQL

What are some alternatives to MySQL, 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.

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.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

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