DBMS > Apache Doris vs. Drizzle vs. Rockset vs. Sphinx vs. SQLite

System Properties Comparison Apache Doris vs. Drizzle vs. Rockset vs. Sphinx vs. SQLite

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

An MPP-based analytics DBMS embracing the MySQL protocol

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS
Search engine

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

rockset.com

sphinxsearch.com

www.sqlite.org

Technical documentation

github.com/apache/doris/wiki

docs.rockset.com

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation, originally contributed from Baidu

Drizzle project, originally started by Brian Aker

Rockset

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2017

2008

2019

2001

2000

Current release

1.2.2, February 2023

7.2.4, September 2012

3.5.1, February 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

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

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

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

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

with proprietary extensions

Read-only SQL queries, including JOINs

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
MySQL client

JDBC

HTTP REST

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

C
C++
Java
PHP

Go
Java
JavaScript (Node.js)
Python

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

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Automatic sharding

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

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

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users and organizations can be defined via Rockset console

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.