DBMS > Datomic vs. EJDB vs. Sphinx vs. SQLite

System Properties Comparison Datomic vs. EJDB vs. Sphinx vs. SQLite

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.datomic.com

github.com/Softmotions/ejdb

sphinxsearch.com

www.sqlite.org

Technical documentation

docs.datomic.com

github.com/Softmotions/ejdb/blob/master/README.md

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Cognitect

Softmotions

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2012

2001

2000

Current release

1.0.7180, July 2024

3.5.1, February 2023

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPLv2

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

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

server-less

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

in-process shared library

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

yes

Transaction Functions

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

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

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

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

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

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

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.