DBMS > KeyDB vs. Linter vs. Snowflake vs. STSdb

System Properties Comparison KeyDB vs. Linter vs. Snowflake vs. STSdb

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

RDBMS for high security requirements

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.80
Rank	#219	Overall
	#31	Key-value stores

Score	0.10
Rank	#350	Overall
	#153	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

github.com/Snapchat/KeyDB
keydb.dev

linter.ru

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

EQ Alpha Technology Ltd.

relex.ru

Snowflake Computing Inc.

STS Soft SC

Initial release

2019

1990

2014

2011

Current release

4.0.8, September 2015

License

Commercial or Open Source

Open Source

BSD-3

commercial

Open Source

GPLv2, commercial license available

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

C and C++

Server operating systems

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Windows

Data scheme

schema-free

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

yes

primitive types and user defined types (classes)

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

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

CLI Client
JDBC
ODBC

.NET Client API

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#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax with the possibility to convert from PL/SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

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

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

fine grained access rights according to SQL-standard

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

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.