DBMS > KeyDB vs. Oracle NoSQL vs. Snowflake vs. TerminusDB

System Properties Comparison KeyDB vs. Oracle NoSQL vs. Snowflake vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Cloud-based data warehousing service for structured and semi-structured data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Document store
Key-value store
Relational DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

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

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

www.oracle.com/database/nosql/technologies/nosql

www.snowflake.com

terminusdb.com

Technical documentation

docs.keydb.dev

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

EQ Alpha Technology Ltd.

Oracle

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2019

2011

2014

2018

Current release

23.3, December 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSD-3

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Open Source

GPL V3

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++

Java

Prolog, Rust

Server operating systems

Linux

Linux
Solaris SPARC/x86

hosted

Linux

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

partial

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

optional

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.

yes

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

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

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

Lua

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

configurable

ACID within a storage node (=shard)

ACID

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 journaling

In-memory capabilities

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

yes

off heap cache

User concepts

Access control

simple password-based access control and ACL

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.