DBMS > Immudb vs. InfinityDB vs. PlanetScale vs. RocksDB

System Properties Comparison Immudb vs. InfinityDB vs. PlanetScale vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

A Java embedded Key-Value Store which extends the Java Map interface

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Key-value store

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

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

Website

github.com/codenotary/immudb
immudb.io

boilerbay.com

planetscale.com

rocksdb.org

Technical documentation

docs.immudb.io

boilerbay.com/infinitydb/manual

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Codenotary

Boiler Bay Inc.

PlanetScale

Facebook, Inc.

Initial release

2020

2002

2020

2013

Current release

1.2.3, April 2022

4.0

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD

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

C++

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

All OS with a Java VM

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

SQL-like syntax

yes

with proprietary extensions

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID at shard level

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.