DBMS > Badger vs. EventStoreDB vs. GeoMesa

System Properties Comparison Badger vs. EventStoreDB vs. GeoMesa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

Primary database model

Key-value store

Event Store

Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Website

github.com/dgraph-io/badger

www.eventstore.com

www.geomesa.org

Technical documentation

godoc.org/github.com/dgraph-io/badger

developers.eventstore.com

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

Developer

DGraph Labs

Event Store Limited

CCRi and others

Initial release

2017

2012

2014

Current release

21.2, February 2021

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

Supported programming languages

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Foreign keys

Referential integrity

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

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.