DBMS > CrateDB vs. JanusGraph vs. SAP HANA

System Properties Comparison CrateDB vs. JanusGraph vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

A Graph DBMS optimized for distributed clusters

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Graph DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.73
Rank	#229	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#8	Vector DBMS

Score	1.91
Rank	#135	Overall
	#12	Graph DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

cratedb.com

janusgraph.org

www.sap.com/products/hana.html

Technical documentation

cratedb.com/docs

docs.janusgraph.org

help.sap.com/hana

Developer

Crate

Linux Foundation; originally developed as Titan by Aurelius

SAP

Initial release

2013

2017

2010

Current release

0.6.3, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

CrateDB Cloud: a distributed SQL database that spreads data and processing across an elastic cluster of shared nothing nodes. CrateDB Cloud enables data insights at scale on Microsoft Azure, AWS and Google Cloud Platform.

Implementation language

Java

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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.

Secondary indexes

yes

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions (Javascript)

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

yes

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

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

In-memory capabilities

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

yes

User concepts

Access control

rights management via user accounts

User authentification and security via Rexster Graph Server

yes

More information provided by the system vendor

Specific characteristics

The enterprise database for time series, documents, and vectors. Distributed - Native...
» more

Competitive advantages

Response time in milliseconds: e ven for complex ad-hoc queries. Massive scaling...
» more

Typical application scenarios

IoT: accelerate your IIoT projects with CrateDB, delivering real-time analytics...
» more

Key customers

Across all continents, CrateDB is used by companies of all sizes to meet the most...
» more

Market metrics

The CrateDB open source project was started in 2013 Honorable Mention in 2021 Gartner®...
» more

Licensing and pricing models

See CrateDB pricing >
» more

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.