DBMS > etcd vs. SingleStore vs. SQLite vs. VelocityDB

System Properties Comparison etcd vs. SingleStore vs. SQLite vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Widely used embeddable, in-process RDBMS

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Key-value store

Relational DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS
	#21	Object oriented DBMS

Website

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

www.singlestore.com

www.sqlite.org

velocitydb.com

Technical documentation

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

docs.singlestore.com

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

SingleStore Inc.

Dwayne Richard Hipp

VelocityDB Inc

Initial release

2013

2000

2011

Current release

3.4, August 2019

8.5, January 2024

3.46.1 (13 August 2024), August 2024

7.x

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free developer edition available

Open Source

Public Domain

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

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux

64 bit version required

server-less

Any that supports .NET

Data scheme

schema-free

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

but no triggers and foreign keys

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC
JSON over HTTP

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

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

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes, watching key changes

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

hash partitioning

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.

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

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

via file-system locks

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Fine grained access control via users, groups and roles

Based on Windows 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.