DBMS > Cachelot.io vs. Geode vs. Google Cloud Datastore vs. LokiJS vs. MySQL

System Properties Comparison Cachelot.io vs. Geode vs. Google Cloud Datastore vs. LokiJS vs. MySQL

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

In-memory JavaScript DBMS

Widely used open source RDBMS

Primary database model

Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

cachelot.io

geode.apache.org

cloud.google.com/datastore

github.com/techfort/LokiJS

www.mysql.com

Technical documentation

geode.apache.org/docs

cloud.google.com/datastore/docs

techfort.github.io/LokiJS

dev.mysql.com/doc

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2002

2008

2014

1995

Current release

1.1, February 2017

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

JavaScript

C and C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

hosted

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

via views

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

Memcached protocol

Java Client API
Memcached protocol
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

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

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

View functions in JavaScript

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

none

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

yes, on a single node

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a single collection possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights per client and object definable

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

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.