DBMS > Apache Druid vs. JanusGraph vs. Snowflake vs. TimesTen

System Properties Comparison Apache Druid vs. JanusGraph vs. Snowflake vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

In-Memory RDBMS compatible to Oracle

Primary database model

Relational DBMS
Time Series DBMS

Graph DBMS

Relational DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

druid.apache.org

janusgraph.org

www.snowflake.com

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

druid.apache.org/docs/latest/design

docs.janusgraph.org

docs.snowflake.net/manuals/index.html

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation and contributors

Linux Foundation; originally developed as Titan by Aurelius

Snowflake Computing Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2017

2014

1998

Current release

29.0.1, April 2024

0.6.3, February 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

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

Linux
OS X
Unix

Linux
OS X
Unix
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-less columns are supported

yes

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

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

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Clojure
Java
Python

JavaScript (Node.js)
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

user defined functions

PL/SQL

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

User authentification and security via Rexster Graph Server

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

fine grained access rights according to SQL-standard

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.