DBMS > Drizzle vs. Lovefield vs. Splice Machine vs. Tkrzw vs. Yaacomo

System Properties Comparison Drizzle vs. Lovefield vs. Splice Machine vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Embeddable relational database for web apps written in pure JavaScript

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

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

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

Website

google.github.io/lovefield

splicemachine.com

dbmx.net/tkrzw

yaacomo.com

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

splicemachine.com/how-it-works

Developer

Drizzle project, originally started by Brian Aker

Google

Splice Machine

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2008

2014

2020

2009

Current release

7.2.4, September 2012

2.1.12, February 2017

3.1, March 2021

0.9.3, August 2020

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

AGPL 3.0, commercial license available

Open Source

Apache Version 2.0

commercial

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++

JavaScript

Java

C++

Server operating systems

FreeBSD
Linux
OS X

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Solaris
Windows

Linux
macOS

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

JDBC

JDBC
Native Spark Datasource
ODBC

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

JavaScript

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Java

Triggers

hooks for callbacks inside the server can be used.

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

using specific database classes

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

fine grained access rights 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.

Related products and services

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

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Machine learning data pipeline outfit Splice Machine files for insolvency
26 August 2021, The Register

Splice Machine Launches the Splice Machine Feature Store to Simplify Feature Engineering and Democratize Machine ...
19 January 2021, PR Newswire

Splice Machine Launches Feature Store to Simplify Feature Engineering
19 January 2021, Datanami

Distributed SQL System Review: Snowflake vs Splice Machine
18 September 2019, Towards Data Science

Splice Machine takes on big boys of big data with Hadoop RDBMS
21 January 2015, RCR Wireless News

provided by Google News

Share this page