DBMS > EJDB vs. MySQL vs. Rockset vs. Sqrrl

System Properties Comparison EJDB vs. MySQL vs. Rockset vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
Spatial DBMS

Relational DBMS
Search engine

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

github.com/Softmotions/ejdb

www.mysql.com

rockset.com

sqrrl.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

docs.rockset.com

Developer

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Amazon

originally Sqrrl Data, Inc.

Initial release

2012

1995

2019

2012

Current release

9.0.0, July 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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++

Java

Server operating systems

server-less

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

dynamic typing

yes

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

yes

SQL

Support of SQL

yes

with proprietary extensions

Read-only SQL queries, including JOINs

APIs and other access methods

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Go
Java
JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

selectable replication factor

making use of Hadoop

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.