DBMS > Datomic vs. Kingbase vs. Snowflake vs. Sphinx

System Properties Comparison Datomic vs. Kingbase vs. Snowflake vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

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

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.50
Rank	#257	Overall
	#119	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

Technical documentation

docs.datomic.com

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Cognitect

BeiJing KINGBASE Information technologies inc.

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2012

1999

2014

2001

Current release

1.0.6735, June 2023

V8.0, August 2021

3.5.1, February 2023

License

Commercial or Open Source

commercial

limited edition free

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

Java, Clojure

C and Java

C++

Server operating systems

All OS with a Java VM

Linux
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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

Standard with numerous extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

Clojure
Java

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning (by range, list and hash) and vertical partitioning

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

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

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

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

recommended only for testing and development

User concepts

Access control

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.