DBMS > ScyllaDB vs. Sphinx vs. SQLite vs. XTDB

System Properties Comparison ScyllaDB vs. Sphinx vs. SQLite vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cassandra and DynamoDB compatible wide column store

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

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Key-value store

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

Score	4.15
Rank	#69	Overall
	#5	Wide column stores

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.scylladb.com

sphinxsearch.com

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.scylladb.com

sphinxsearch.com/docs

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

ScyllaDB

Sphinx Technologies Inc.

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2015

2001

2000

2019

Current release

ScyllaDB Open Source 6.0.2, July 2024

3.5.1, February 2023

3.46.1 (13 August 2024), August 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Open Source (AGPL), commercial license available

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

Open Source

MIT License

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

Clojure

Server operating systems

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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

cluster global secondary indices

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like DML and DDL statements (CQL)

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

Supported programming languages

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, 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

Clojure
Java

Server-side scripts

Stored procedures

yes, Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

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

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

in-memory tables

yes

User concepts

Access control

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.