DBMS > CockroachDB vs. HBase vs. Sphinx vs. SQLite

System Properties Comparison CockroachDB vs. HBase vs. Sphinx vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Wide-column store based on Apache Hadoop and on concepts of BigTable

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	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.cockroachlabs.com

hbase.apache.org

sphinxsearch.com

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

hbase.apache.org/book.html

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Cockroach Labs

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2015

2008

2001

2000

Current release

23.1.1, May 2023

2.3.4, January 2021

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache version 2

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

C++

Server operating systems

Linux
macOS
Windows

Linux
Unix
Windows

using Cygwin

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

dynamic schema

schema-free, schema definition possible

yes

dynamic column types

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

yes, wire compatible with PostgreSQL

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

Java API
RESTful HTTP API
Thrift

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

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

User concepts

Access control

Role-based access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.