DBMS > EJDB vs. PlanetScale vs. Sequoiadb vs. SQLite

System Properties Comparison EJDB vs. PlanetScale vs. Sequoiadb vs. SQLite

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)

Scalable, distributed, serverless MySQL database platform built on top of Vitess

NewSQL database with distributed OLTP and SQL

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/Softmotions/ejdb

planetscale.com

www.sequoiadb.com

www.sqlite.org

Technical documentation

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

planetscale.com/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

www.sqlite.org/docs.html

Developer

Softmotions

PlanetScale

Sequoiadb Ltd.

Dwayne Richard Hipp

Initial release

2012

2020

2013

2000

Current release

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

Public Domain

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

Server operating systems

server-less

Docker
Linux
macOS

Linux

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

oid, date, timestamp, binary, regex

yes

not rigid because of 'dynamic typing' concept.

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

with proprietary extensions

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

in-process shared library

ADO.NET
JDBC
MySQL protocol
ODBC

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

.Net
C++
Java
PHP
Python

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

Server-side scripts

Stored procedures

yes

proprietary syntax

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency across shards
Immediate Consistency within a shard

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

yes

via file-system locks

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

simple password-based access control

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.