DBMS > Apache Drill vs. Oracle vs. PlanetScale vs. TinkerGraph

System Properties Comparison Apache Drill vs. Oracle vs. PlanetScale vs. TinkerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Widely used RDBMS

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store
Relational DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

drill.apache.org

www.oracle.com/database

planetscale.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

drill.apache.org/docs

docs.oracle.com/en/database

planetscale.com/docs

Developer

Apache Software Foundation

Oracle

PlanetScale

Initial release

2012

1980

2020

2009

Current release

1.20.3, January 2023

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux
macOS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

schema-free

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 SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

TinkerPop 3

Supported programming languages

C++

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

isolation level can be parameterized

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

Depending on the underlying data source

yes

optional

In-memory capabilities

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

Depending on the underlying data source

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

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.