DBMS > Dolt vs. EXASOL vs. Lovefield vs. SiteWhere vs. Snowflake

System Properties Comparison Dolt vs. EXASOL vs. Lovefield vs. SiteWhere vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Embeddable relational database for web apps written in pure JavaScript

M2M integration platform for persisting/querying time series data

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.exasol.com

google.github.io/lovefield

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

docs.dolthub.com

www.exasol.com/resources

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

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

DoltHub Inc

Exasol

Google

SiteWhere

Snowflake Computing Inc.

Initial release

2018

2000

2014

2010

2014

Current release

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.0

commercial

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.

Implementation language

JavaScript

Java

Server operating systems

Linux
macOS
Windows

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Windows

hosted

Data scheme

yes

predefined scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

CLI Client
HTTP REST

.Net
JDBC
ODBC
WebSocket

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

Triggers

yes

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

none

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop 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

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

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

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

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

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.