DBMS > etcd vs. GridDB vs. Quasardb vs. SQLite

System Properties Comparison etcd vs. GridDB vs. Quasardb vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

Scalable in-memory time series database optimized for IoT and Big Data

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
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	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

griddb.net

quasar.ai

www.sqlite.org

Technical documentation

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

docs.griddb.net

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

Toshiba Corporation

quasardb

Dwayne Richard Hipp

Initial release

2013

2009

2000

Current release

3.4, August 2019

5.1, August 2022

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux

BSD
Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC
JSON over HTTP

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

none

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

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Access rights for users can be defined per database

Cryptographically strong user authentication and audit trail

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.