DBMS > Oracle Coherence vs. OrientDB vs. PlanetScale vs. Snowflake

System Properties Comparison Oracle Coherence vs. OrientDB vs. PlanetScale vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Oracles in-memory data grid solution

Multi-model DBMS (Document, Graph, Key/Value)

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.oracle.com/java/coherence

orientdb.org

planetscale.com

www.snowflake.com

Technical documentation

docs.oracle.com/en/middleware/standalone/coherence

www.orientdb.com/docs/last/index.html

planetscale.com/docs

docs.snowflake.net/manuals/index.html

Developer

Oracle

OrientDB LTD; CallidusCloud; SAP

PlanetScale

Snowflake Computing Inc.

Initial release

2007

2010

2020

2014

Current release

14.1, August 2023

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

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

Server operating systems

All OS with a Java VM

All OS with a Java JDK (>= JDK 6)

Docker
Linux
macOS

hosted

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

with proprietary extensions

yes

APIs and other access methods

JCache
JPA
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C++
Java

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java, Javascript

yes

proprietary syntax

user defined functions

Triggers

yes

Live Events

Hooks

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with selectable consistency level

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

not for MyISAM storage engine

yes

Transaction concepts

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

configurable

ACID

ACID at shard level

ACID

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

optionally

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

authentification to access the cache via certificates or http basic authentication

Access rights for users and roles; record level security configurable

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.