DBMS > MySQL vs. Percona Server for MongoDB vs. Rockset vs. SWC-DB

System Properties Comparison MySQL vs. Percona Server for MongoDB vs. Rockset vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A scalable, reliable search and analytics service in the cloud, built on RocksDB

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Wide column store

Secondary database models

Document store
Spatial DBMS

Relational DBMS
Search engine

Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Website

www.mysql.com

www.percona.com/mongodb/software/percona-server-for-mongodb

rockset.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

dev.mysql.com/doc

docs.percona.com/percona-distribution-for-mongodb

docs.rockset.com

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Percona

Rockset

Alex Kashirin

Initial release

1995

2015

2019

2020

Current release

9.0.0, July 2024

3.4.10-2.10, November 2017

0.5, April 2021

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL Version 2

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

Read-only SQL queries, including JOINs

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

HTTP REST

Proprietary protocol
Thrift

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Go
Java
JavaScript (Node.js)
Python

C++

Server-side scripts

Stored procedures

yes

proprietary syntax

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

Access rights for users and organizations can be defined via Rockset console

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.