DBMS > Databend vs. Datomic vs. Dgraph vs. RocksDB vs. Sphinx

System Properties Comparison Databend vs. Datomic vs. Dgraph vs. RocksDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Distributed and scalable native Graph DBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

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

Score	0.30
Rank	#287	Overall
	#130	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

github.com/datafuselabs/databend
www.databend.com

Technical documentation

docs.databend.com

docs.datomic.com

dgraph.io/docs

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Databend Labs

Cognitect

Dgraph Labs, Inc.

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2021

2012

2016

2013

2001

Current release

1.0.59, April 2023

1.0.6735, June 2023

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

Rust

Java, Clojure

C++

Server operating systems

hosted
Linux
macOS

All OS with a Java VM

Linux
OS X
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

C++ API
Java API

Proprietary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

Clojure
Java

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Transaction Functions

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Synchronous replication via Raft

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Users with fine-grained authorization concept, user roles

Planned for future releases

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.