DBMS > Dolt vs. Firebase Realtime Database vs. Snowflake vs. Sphinx

System Properties Comparison Dolt vs. Firebase Realtime Database vs. Snowflake vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

github.com/dolthub/dolt
www.dolthub.com

firebase.google.com/products/realtime-database

www.snowflake.com

sphinxsearch.com

Technical documentation

docs.dolthub.com

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

DoltHub Inc

Google

acquired by Google 2014

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2018

2012

2014

2001

Current release

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

Linux
macOS
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

CLI Client
HTTP REST

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

currently in alpha release

limited functionality with using 'rules'

user defined functions

Triggers

yes

Callbacks are triggered when data changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

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.

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

yes, based on authentication and database rules

Users with fine-grained authorization concept, user roles and pluggable authentication

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.