DBMS > etcd vs. GeoMesa vs. KeyDB vs. OrigoDB

System Properties Comparison etcd vs. GeoMesa vs. KeyDB vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

A fully ACID in-memory object graph database

Primary database model

Key-value store

Spatial DBMS

Key-value store

Document store
Object oriented DBMS

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

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

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

www.geomesa.org

github.com/Snapchat/KeyDB
keydb.dev

origodb.com

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

docs.keydb.dev

origodb.com/docs

Developer

CCRi and others

EQ Alpha Technology Ltd.

Robert Friberg et al

Initial release

2014

2019

2009

under the name LiveDB

Current release

3.4, August 2019

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

BSD-3

Open Source

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

Scala

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

APIs and other access methods

gRPC
JSON over HTTP

Proprietary protocol

RESP - REdis Serialization Protoco

.NET Client API
HTTP API
LINQ

Supported programming languages

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net

Server-side scripts

Stored procedures

Lua

yes

Triggers

yes, watching key changes

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

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

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

Write ahead log

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control and ACL

Role based authorization

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Monitor Amazon EKS Control Plane metrics using AWS Open Source monitoring services | Amazon Web Services
12 October 2023, AWS Blog

RBI reiterates need for underlying forex exposure for rupee derivatives transactions | Stock Market News
5 April 2024, Mint

6 Cool Kubernetes Operators and How to Use Them
22 January 2024, hackernoon.com

Killing a market, softly: How an RBI communique could end India's thriving ETCD market
7 April 2024, The Economic Times

ETCD directives don't go well with RBI's stellar reputation
14 April 2024, Business Standard

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Share this page