DBMS > Oracle vs. PlanetScale vs. Titan

System Properties Comparison Oracle vs. PlanetScale vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Widely used RDBMS

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

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	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

www.oracle.com/database

planetscale.com

github.com/thinkaurelius/titan

Technical documentation

docs.oracle.com/en/database

planetscale.com/docs

github.com/thinkaurelius/titan/wiki

Developer

Oracle

PlanetScale

Aurelius, owned by DataStax

Initial release

1980

2020

2012

Current release

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache license, version 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

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

Docker
Linux
macOS

Linux
OS X
Unix
Windows

Data scheme

yes

Schemaless in JSON and XML columns

yes

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

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

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

Clojure
Java
Python

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graph

Transaction concepts

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

ACID

isolation level can be parameterized

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

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

yes

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

User authentification and security via Rexster Graph Server

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.