DBMS > EJDB vs. OrigoDB vs. PlanetScale vs. Quasardb

System Properties Comparison EJDB vs. OrigoDB vs. PlanetScale vs. Quasardb

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 fully ACID in-memory object graph database

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

Distributed, high-performance timeseries database

Primary database model

Document store

Document store
Object oriented DBMS

Relational DBMS

Time Series 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	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

github.com/Softmotions/ejdb

origodb.com

planetscale.com

quasar.ai

Technical documentation

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

origodb.com/docs

planetscale.com/docs

doc.quasar.ai/master

Developer

Softmotions

Robert Friberg et al

PlanetScale

quasardb

Initial release

2012

2009

under the name LiveDB

2020

2009

Current release

3.14.1, January 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Linux
Windows

Docker
Linux
macOS

BSD
Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

User defined using .NET types and collections

yes

integer and binary

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.

can be achieved using .NET

Secondary indexes

yes

with tags

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

in-process shared library

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP API

Supported programming languages

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

.Net

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

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 across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

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

Write ahead log

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Role based authorization

Users with fine-grained authorization concept

no user groups or roles

Cryptographically strong user authentication and audit trail

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

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Ranked Number 188 Fastest-Growing Company in North America on the 2023 Deloitte Technology Fast ...
8 November 2023, Business Wire

PlanetScale Ranked Number 188 Fastest-Growing Company in North America on the 2023 Deloitte Technology Fast ...
8 November 2023, Yahoo Finance

PlanetScale Insights Anomalies introduces smart query monitoring
29 November 2023, SDTimes.com

provided by Google News

Hubble Unexpectedly Finds Double Quasar in Distant Universe
4 October 2023, Science@NASA

Record quasar is most luminous object in the universe
20 February 2024, EarthSky

Quasar Partners with PTC to Empower IoT Customers with High-Performance Data Solutions
11 September 2023, Datanami

Quasar Selected by National Renewable Energy Laboratory to Help with Energy System De-risking and Optimization
6 June 2023, PR Newswire

QUASAR yacht (Bilgin, 46.8m, 2016)
3 July 2023, Boat International

provided by Google News

Share this page