DBMS > Apache Doris vs. OrigoDB vs. PlanetScale vs. RocksDB vs. Sequoiadb

System Properties Comparison Apache Doris vs. OrigoDB vs. PlanetScale vs. RocksDB vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

A fully ACID in-memory object graph database

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Key-value store

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

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

Website

doris.apache.org
github.com/apache/doris

Technical documentation

github.com/apache/doris/wiki

origodb.com/docs

planetscale.com/docs

github.com/facebook/rocksdb/wiki

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

Developer

Apache Software Foundation, originally contributed from Baidu

Robert Friberg et al

PlanetScale

Facebook, Inc.

Sequoiadb Ltd.

Initial release

2017

2009

under the name LiveDB

2020

2013

Current release

1.2.2, February 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

commercial

Open Source

BSD

Open Source

Server: AGPL; Client: Apache V2

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

Java

C++

Server operating systems

Linux

Linux
Windows

Docker
Linux
macOS

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
MySQL client

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

proprietary protocol using JSON

Supported programming languages

Java

.Net

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

JavaScript

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Eventual Consistency

Foreign keys

Referential integrity

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

yes

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Role based authorization

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.