DBMS > Galaxybase vs. Geode vs. PouchDB vs. Splice Machine vs. SQLite

System Properties Comparison Galaxybase vs. Geode vs. PouchDB vs. Splice Machine vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Scalable, ACID-compliant native distributed parallel graph platform

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

JavaScript DBMS with an API inspired by CouchDB

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

geode.apache.org/docs

pouchdb.com/guides

splicemachine.com/how-it-works

www.sqlite.org/docs.html

Developer

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

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

Apache Software Foundation

Splice Machine

Dwayne Richard Hipp

Initial release

2017

2002

2012

2014

2000

Current release

Nov 20, November 2021

1.1, February 2017

7.1.1, June 2019

3.1, March 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

AGPL 3.0, commercial license available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and Java

Java

JavaScript

Java

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

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

Linux
OS X
Solaris
Windows

server-less

Data scheme

Strong typed schema

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

via views

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
Native Spark Datasource
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
Python

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

JavaScript

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined procedures and functions

user defined functions

View functions in JavaScript

yes

Java

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Role-based access control

Access rights per client and object definable

Access rights for users, groups and roles according to SQL-standard

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.