DBMS > EJDB vs. Splice Machine vs. SQLite vs. YugabyteDB

System Properties Comparison EJDB vs. Splice Machine vs. SQLite vs. YugabyteDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Widely used embeddable, in-process RDBMS

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Wide column store

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	2.91
Rank	#102	Overall
	#51	Relational DBMS

Website

github.com/Softmotions/ejdb

splicemachine.com

www.sqlite.org

www.yugabyte.com

Technical documentation

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

splicemachine.com/how-it-works

www.sqlite.org/docs.html

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

Softmotions

Splice Machine

Dwayne Richard Hipp

Yugabyte Inc.

Initial release

2012

2014

2000

2017

Current release

3.1, March 2021

3.45.3 (15 April 2024), April 2024

2.19, September 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

AGPL 3.0, commercial license available

Open Source

Public Domain

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

Java

C and C++

Server operating systems

server-less

Linux
OS X
Solaris
Windows

server-less

Linux
OS X

Data scheme

schema-free

yes

dynamic column types

depending on used data model

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes, PostgreSQL compatible

APIs and other access methods

in-process shared library

JDBC
Native Spark Datasource
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes

Java

yes

sql, plpgsql, C

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

based on RocksDB

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» more

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.