DBMS > FatDB vs. InfinityDB vs. KeyDB vs. Memcached vs. RocksDB

System Properties Comparison FatDB vs. InfinityDB vs. KeyDB vs. Memcached vs. RocksDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

In-memory key-value store, originally intended for caching

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

Primary database model

Document store
Key-value store

Key-value store

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

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

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

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

Website

boilerbay.com

github.com/Snapchat/KeyDB
keydb.dev

www.memcached.org

rocksdb.org

Technical documentation

boilerbay.com/infinitydb/manual

docs.keydb.dev

github.com/memcached/memcached/wiki

github.com/facebook/rocksdb/wiki

Developer

FatCloud

Boiler Bay Inc.

EQ Alpha Technology Ltd.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Facebook, Inc.

Initial release

2012

2002

2019

2003

2013

Current release

4.0

1.6.27, May 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

BSD license

Open Source

BSD

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

Java

C++

Server operating systems

Windows

All OS with a Java VM

Linux

FreeBSD
Linux
OS X
Unix
Windows

Linux

Data scheme

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

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

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Proprietary protocol

RESP - REdis Serialization Protoco

Proprietary protocol

C++ API
Java API

Supported programming languages

Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Lua

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

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

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

Optimistic locking, atomic execution of commands blocks and scripts

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Can implement custom security layer via applications

simple password-based access control and ACL

yes

using SASL (Simple Authentication and Security Layer) protocol

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.