DBMS > Cubrid vs. Riak KV vs. Snowflake vs. Typesense

System Properties Comparison Cubrid vs. Riak KV vs. Snowflake vs. Typesense

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Distributed, fault tolerant key-value store

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

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Search engine

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.76
Rank	#219	Overall
	#14	Search engines

Website

cubrid.com (korean)
cubrid.org (english)

www.snowflake.com

typesense.org

Technical documentation

cubrid.org/manuals

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

typesense.org/docs

Developer

CUBRID Corporation, CUBRID Foundation

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2008

2009

2014

2015

Current release

11.0, January 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

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, C++, Java

Erlang

C++

Server operating systems

Linux
Windows

Linux
OS X

hosted

Linux

Data scheme

yes

schema-free

yes

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

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

yes, using Riak Security

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.