DBMS > Datomic vs. PostGIS vs. RocksDB vs. SAP SQL Anywhere vs. Sphinx

System Properties Comparison Datomic vs. PostGIS vs. RocksDB vs. SAP SQL Anywhere vs. Sphinx

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

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Secondary database models

Relational DBMS

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

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

www.datomic.com

postgis.net

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

sphinxsearch.com

Technical documentation

docs.datomic.com

postgis.net/documentation

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

sphinxsearch.com/docs

Developer

Cognitect

Facebook, Inc.

SAP

formerly Sybase

Sphinx Technologies Inc.

Initial release

2012

2005

2013

1992

2001

Current release

1.0.6735, June 2023

3.4.2, February 2024

8.11.4, April 2024

17, July 2015

3.5.1, February 2023

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPL v2.0

Open Source

BSD

commercial

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

C++

Server operating systems

All OS with a Java VM

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

RESTful HTTP API

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Proprietary protocol

Supported programming languages

Clojure
Java

C
C++
Go
Java
Perl
Python
Ruby

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

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

yes, in C/C++, Java, .Net or Perl

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

based on PostgreSQL

horizontal partitioning

none

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

based on PostgreSQL

yes

Source-replica replication

Database mirroring

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

yes

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

yes

User concepts

Access control

yes

based on PostgreSQL

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.