DBMS > Greenplum vs. Oracle NoSQL vs. SQLite vs. Titan

System Properties Comparison Greenplum vs. Oracle NoSQL vs. SQLite 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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Widely used embeddable, in-process RDBMS

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

greenplum.org

www.oracle.com/database/nosql/technologies/nosql

www.sqlite.org

github.com/thinkaurelius/titan

Technical documentation

docs.greenplum.org

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.sqlite.org/docs.html

github.com/thinkaurelius/titan/wiki

Developer

Pivotal Software Inc.

Oracle

Dwayne Richard Hipp

Aurelius, owned by DataStax

Initial release

2005

2011

2000

2012

Current release

7.0.0, September 2023

23.3, December 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Public Domain

Open Source

Apache license, version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

Linux

Linux
Solaris SPARC/x86

server-less

Linux
OS X
Unix
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

since Version 4.2

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C
Java
Perl
Python
R

C
C#
Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and 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.