DBMS > etcd vs. SiteWhere vs. SQLite vs. VoltDB

System Properties Comparison etcd vs. SiteWhere vs. SQLite vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

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

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

etcd.io
github.com/etcd-io/etcd

github.com/sitewhere/sitewhere

www.sqlite.org

www.voltdb.com

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

docs.voltdb.com

Developer

SiteWhere

Dwayne Richard Hipp

VoltDB Inc.

Initial release

2010

2000

2010

Current release

3.4, August 2019

3.46.0 (23 May 2024), May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

Java, C++

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux
OS X
Windows

server-less

Linux
OS X

for development

Data scheme

schema-free

predefined scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

gRPC
JSON over HTTP

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

selectable replication factor

based on HBase

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

Users and roles with access to stored procedures

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.