DBMS > Geode vs. Lovefield vs. Splunk vs. Tkrzw

System Properties Comparison Geode vs. Lovefield vs. Splunk vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Geode  Xexclude from comparison	Lovefield  Xexclude from comparison	Splunk  Xexclude from comparison	Tkrzw Successor of Tokyo Cabinet and Kyoto Cabinet  Xexclude from comparison
Description	Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes	Embeddable relational database for web apps written in pure JavaScript	Analytics Platform for Big Data	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	Key-value store	Relational DBMS	Search engine	Key-value store
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 1.67 Rank #138   Overall #26   Key-value stores	Score 0.20 Rank #290   Overall #136   Relational DBMS	Score 98.21 Rank #14   Overall #2   Search engines	Score 0.00 Rank #356   Overall #57   Key-value stores
Website	geode.apache.org	google.github.io/­lovefield	www.splunk.com	dbmx.net/­tkrzw
Technical documentation	geode.apache.org/­docs	github.com/­google/­lovefield/­blob/­master/­docs/­spec_index.md	docs.splunk.com/­Documentation/­Splunk
Developer	Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.	Google	Splunk Inc.	Mikio Hirabayashi
Initial release	2002	2014	2003	2020
Current release	1.1, February 2017	2.1.12, February 2017		0.9.3, August 2020
License Commercial or Open Source	Open Source Apache Version 2; commercial licenses available as Gemfire	Open Source Apache 2.0	commercial Limited free edition and free developer edition available	Open Source Apache Version 2.0
Cloud-based only Only available as a cloud service	no	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Java	JavaScript		C++
Server operating systems	All OS with a Java VM the JDK (8 or later) is also required	server-less, requires a JavaScript environment (browser, Node.js) tested with Chrome, Firefox, IE, Safari	Linux OS X Solaris Windows	Linux macOS
Data scheme	schema-free	yes	yes	schema-free
Typing predefined data types such as float or date	yes	yes	yes	no
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.	no	no	yes	no
Secondary indexes	no	yes	yes
SQL Support of SQL	SQL-like query language (OQL)	SQL-like query language via JavaScript builder pattern	no Splunk Search Processing Language for search commands	no
APIs and other access methods	Java Client API Memcached protocol RESTful HTTP API		HTTP REST
Supported programming languages	.Net All JVM based languages C++ Groovy Java Scala	JavaScript	C# Java JavaScript PHP Python Ruby	C++ Java Python Ruby
Server-side scripts Stored procedures	user defined functions	no	yes	no
Triggers	yes Cache Event Listeners	Using read-only observers	yes	no
Partitioning methods Methods for storing different data on different nodes	Sharding	none	Sharding	none
Replication methods Methods for redundantly storing data on multiple nodes	Multi-source replication	none	Multi-source replication	none
MapReduce Offers an API for user-defined Map/Reduce methods	no	no	yes	no
Consistency concepts Methods to ensure consistency in a distributed system	Eventual Consistency		Eventual Consistency	Immediate Consistency
Foreign keys Referential integrity	no	yes	no	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	yes, on a single node	ACID	no A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching
Concurrency Support for concurrent manipulation of data	yes	yes	yes	yes
Durability Support for making data persistent	yes	yes, by using IndexedDB or the cloud service Firebase Realtime Database	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes	yes using MemoryDB	no	yes using specific database classes
User concepts Access control	Access rights per client and object definable	no	Access rights for users and roles	no
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
	Geode	Lovefield	Splunk	Tkrzw Successor of Tokyo Cabinet and Kyoto Cabinet
DB-Engines blog posts