DBMS > Cubrid vs. HyperSQL vs. Memcached vs. Snowflake vs. Sphinx

System Properties Comparison Cubrid vs. HyperSQL vs. Memcached vs. Snowflake vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

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

Technical documentation

cubrid.org/manuals

hsqldb.org/web/hsqlDocsFrame.html

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

CUBRID Corporation, CUBRID Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2008

2001

2003

2014

2001

Current release

11.0, January 2021

2.7.2, June 2023

1.6.27, May 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

based on BSD license

Open Source

BSD license

commercial

Open Source

GPL version 2, commercial licence 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++, Java

Java

C++

Server operating systems

Linux
Windows

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

FreeBSD
Linux
OS X
Unix
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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

yes

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

HTTP API

JDBC via HTTP
JDBC
ODBC

Proprietary protocol

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

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

All languages supporting JDBC/ODBC
Java

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

Java, SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

The original contents of fields are not stored in the Sphinx index.

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 SASL (Simple Authentication and Security Layer) protocol

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.