DBMS > EJDB vs. Oracle NoSQL vs. Vitess

System Properties Comparison EJDB vs. Oracle NoSQL vs. Vitess

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)

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

Document store
Key-value 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.27
Rank	#297	Overall
	#44	Document stores

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/Softmotions/ejdb

www.oracle.com/database/nosql/technologies/nosql

vitess.io

Technical documentation

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

vitess.io/docs

Developer

Softmotions

Oracle

The Linux Foundation, PlanetScale

Initial release

2012

2011

2013

Current release

23.3, December 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Apache Version 2.0, commercial licenses available

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.

Implementation language

Java

Server operating systems

server-less

Linux
Solaris SPARC/x86

Docker
Linux
macOS

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

optional

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

in-process shared library

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

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

configurable

ACID within a storage node (=shard)

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

off heap cache

yes

User concepts

Access control

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Enhance enterprise data security and trust: Must see Blockchain Technology sessions at Oracle CloudWorld 2023
21 August 2023, Oracle

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, Oracle

Oracle Beefs Up Its NoSQL Database Offering
3 April 2014, Data Center Knowledge

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

Larry Ellison Just Embraced the Enemy. Or Did He?
1 October 2012, WIRED

provided by Google News

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page