DBMS > Alibaba Cloud Table Store vs. Cubrid vs. Datomic vs. Prometheus vs. SQLite

System Properties Comparison Alibaba Cloud Table Store vs. Cubrid vs. Datomic vs. Prometheus vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Open-source Time Series DBMS and monitoring system

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.alibabacloud.com/product/table-store

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

www.datomic.com

prometheus.io

www.sqlite.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

cubrid.org/manuals

docs.datomic.com

prometheus.io/docs

www.sqlite.org/docs.html

Developer

Alibaba

CUBRID Corporation, CUBRID Foundation

Cognitect

Dwayne Richard Hipp

Initial release

2016

2008

2012

2015

2000

Current release

11.0, January 2021

1.0.6735, June 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

Apache 2.0

Open Source

Public Domain

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, Clojure

Server operating systems

hosted

Linux
Windows

All OS with a Java VM

Linux
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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.

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
Python

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

Clojure
Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Transaction Functions

Triggers

yes

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

none

But extensive use of caching in the application peers

yes

by Federation

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights based on subaccounts and tokens

fine grained access rights according to SQL-standard

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.