DBMS > EventStoreDB vs. Google Cloud Bigtable vs. RocksDB vs. Valentina Server

System Properties Comparison EventStoreDB vs. Google Cloud Bigtable vs. RocksDB vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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

Object-relational database and reports server

Primary database model

Event Store

Key-value store
Wide column store

Key-value store

Relational DBMS

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

www.eventstore.com

cloud.google.com/bigtable

rocksdb.org

www.valentina-db.net

Technical documentation

developers.eventstore.com

cloud.google.com/bigtable/docs

github.com/facebook/rocksdb/wiki

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Event Store Limited

Google

Facebook, Inc.

Paradigma Software

Initial release

2012

2015

2013

1999

Current release

21.2, February 2021

9.2.1, May 2024

5.7.5

License

Commercial or Open Source

Open Source

commercial

Open Source

BSD

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

C++

Server operating systems

Linux
Windows

hosted

Linux

Linux
OS X
Windows

Data scheme

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

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

C++ API
Java API

ODBC

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.