DB-EnginesInfluxDB: Focus on building software with an easy-to-use serverless, scalable time series platformEnglish
Deutsch
Knowledge Base of Relational and NoSQL Database Management Systemsprovided by solid IT

DBMS > GBase vs. Google Cloud Firestore vs. Ignite vs. Sphinx vs. Tkrzw

System Properties Comparison GBase vs. Google Cloud Firestore vs. Ignite vs. Sphinx vs. Tkrzw

Editorial information provided by DB-Engines
NameGBase  Xexclude from comparisonGoogle Cloud Firestore  Xexclude from comparisonIgnite  Xexclude from comparisonSphinx  Xexclude from comparisonTkrzw infoSuccessor of Tokyo Cabinet and Kyoto Cabinet  Xexclude from comparison
DescriptionAn analytical database for business intelligence with large customers in China.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.Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.Open source search engine for searching in data from different sources, e.g. relational databasesA 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 modelRelational DBMSDocument storeKey-value store
Relational DBMS
Search engineKey-value store
DB-Engines Ranking infomeasures the popularity of database management systemsranking trend
Trend Chart
Score1.16
Rank#163  Overall
#77  Relational DBMS
Score9.09
Rank#53  Overall
#10  Document stores
Score6.85
Rank#62  Overall
#7  Key-value stores
#35  Relational DBMS
Score7.29
Rank#60  Overall
#8  Search engines
Score0.00
Rank#356  Overall
#57  Key-value stores
Websitewww.gbase8a.comfirebase.google.com/­products/­firestoreignite.apache.orgsphinxsearch.comdbmx.net/­tkrzw
Technical documentationfirebase.google.com/­docs/­firestoreapacheignite.readme.io/­docssphinxsearch.com/­docs
DeveloperGoogleApache Software FoundationSphinx Technologies Inc.Mikio Hirabayashi
Initial release2017201520012020
Current releaseGBase 8aApache Ignite 2.63.4.1, July 20210.9.3, August 2020
License infoCommercial or Open SourcecommercialcommercialOpen Source infoApache 2.0Open Source infoGPL version 2, commercial licence availableOpen Source infoApache Version 2.0
Cloud-based only infoOnly available as a cloud servicenoyesnonono
DBaaS offerings (sponsored links) infoDatabase as a Service

Providers of DBaaS offerings, please contact us to be listed.
Implementation languageC++, Java, .NetC++C++
Server operating systemshostedLinux
OS X
Solaris
Windows
FreeBSD
Linux
NetBSD
OS X
Solaris
Windows
Linux
macOS
Data schemeschema-freeyesyesschema-free
Typing infopredefined data types such as float or dateyesyesnono
XML support infoSome form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.noyesno
Secondary indexesyesyesyes infofull-text index on all search fields
SQL infoSupport of SQLnoANSI-99 for query and DML statements, subset of DDLSQL-like query language (SphinxQL)no
APIs and other access methodsAndroid
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API
HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data
Proprietary protocol
Supported programming languagesGo
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python
C#
C++
Java
PHP
Python
Ruby
Scala
C++ infounofficial client library
Java
Perl infounofficial client library
PHP
Python
Ruby infounofficial client library
C++
Java
Python
Ruby
Server-side scripts infoStored proceduresyes, Firebase Rules & Cloud Functionsyes (compute grid and cache interceptors can be used instead)nono
Triggersyes, with Cloud Functionsyes (cache interceptors and events)nono
Partitioning methods infoMethods for storing different data on different nodesShardingShardingSharding infoPartitioning is done manually, search queries against distributed index is supportednone
Replication methods infoMethods for redundantly storing data on multiple nodesMulti-source replicationyes (replicated cache)nonenone
MapReduce infoOffers an API for user-defined Map/Reduce methodsUsing Cloud Dataflowyes (compute grid and hadoop accelerator)nono
Consistency concepts infoMethods to ensure consistency in a distributed systemImmediate ConsistencyImmediate ConsistencyImmediate Consistency
Foreign keys infoReferential integritynononono
Transaction concepts infoSupport to ensure data integrity after non-atomic manipulations of datayesACIDno
Concurrency infoSupport for concurrent manipulation of datayesyesyesyes
Durability infoSupport for making data persistentyesyesyes infoThe original contents of fields are not stored in the Sphinx index.yes
In-memory capabilities infoIs there an option to define some or all structures to be held in-memory only.yesyes infousing specific database classes
User concepts infoAccess controlAccess rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.Security Hooks for custom implementationsnono

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources
GBaseGoogle Cloud FirestoreIgniteSphinxTkrzw infoSuccessor of Tokyo Cabinet and Kyoto Cabinet
DB-Engines blog posts