DBMS > AgensGraph vs. Couchbase vs. Google Cloud Firestore vs. Sphinx vs. Tkrzw

System Properties Comparison AgensGraph vs. Couchbase vs. Google Cloud Firestore vs. Sphinx vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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.

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

Graph DBMS
Relational DBMS

Document store

Search engine

Key-value store

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

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

Website

bitnine.net/agensgraph

www.couchbase.com

firebase.google.com/products/firestore

sphinxsearch.com

dbmx.net/tkrzw

Technical documentation

bitnine.net/documentation

docs.couchbase.com

firebase.google.com/docs/firestore

sphinxsearch.com/docs

Developer

Bitnine Global Inc.

Couchbase, Inc.

Google

Sphinx Technologies Inc.

Mikio Hirabayashi

Initial release

2016

2011

2017

2001

2020

Current release

2.1, December 2018

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.5.1, February 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

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, C++, Go and Erlang

C++

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS

Data scheme

depending on used data model

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

yes

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like query language (SphinxQL)

APIs and other access methods

Cypher Query Language
JDBC

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

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

Proprietary protocol

Supported programming languages

C
Java
JavaScript
Python

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

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

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes, Firebase Rules & Cloud Functions

Triggers

yes

via the TAP protocol

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

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

Source-replica replication

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Ephemeral buckets

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

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.