DBMS > Coveo vs. Google Cloud Firestore vs. RocksDB vs. Sphinx vs. Tkrzw

System Properties Comparison Coveo vs. Google Cloud Firestore vs. RocksDB vs. Sphinx vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.coveo.com

firebase.google.com/products/firestore

rocksdb.org

sphinxsearch.com

dbmx.net/tkrzw

Technical documentation

docs.coveo.com

firebase.google.com/docs/firestore

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Coveo

Google

Facebook, Inc.

Sphinx Technologies Inc.

Mikio Hirabayashi

Initial release

2012

2017

2013

2001

2020

Current release

8.11.4, April 2024

3.5.1, February 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Open Source

Apache Version 2.0

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

hosted

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

schema-free

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

C++ API
Java API

Proprietary protocol

Supported programming languages

C#
Java
JavaScript
Python

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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.

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

granular access controls, API key management, content filters

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.