DBMS > KeyDB vs. NSDb vs. Snowflake vs. Vertica

System Properties Comparison KeyDB vs. NSDb vs. Snowflake vs. Vertica

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

nsdb.io

www.snowflake.com

www.vertica.com

Technical documentation

docs.keydb.dev

nsdb.io/Architecture

docs.snowflake.net/manuals/index.html

vertica.com/documentation

Developer

EQ Alpha Technology Ltd.

Snowflake Computing Inc.

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2019

2017

2014

2005

Current release

12.0.3, January 2023

License

Commercial or Open Source

Open Source

BSD-3

Open Source

Apache Version 2.0

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java, Scala

C++

Server operating systems

Linux

Linux
macOS

hosted

Linux

Data scheme

schema-free

yes

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

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

yes: int, bigint, decimal, string

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

all fields are automatically indexed

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

SQL-like query language

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

gRPC
HTTP REST
WebSocket

CLI Client
JDBC
ODBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

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

Java
Scala

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

Lua

user defined functions

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

similar concept for controling cloud resources

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency

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

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

Using Apache Lucene

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

simple password-based access control and ACL

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

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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.