DBMS > Badger vs. GeoMesa vs. Linter vs. SpatiaLite

System Properties Comparison Badger vs. GeoMesa vs. Linter vs. SpatiaLite

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.

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

RDBMS for high security requirements

Spatial extension of SQLite

Primary database model

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

github.com/dgraph-io/badger

www.geomesa.org

linter.ru

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

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

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

DGraph Labs

CCRi and others

relex.ru

Alessandro Furieri

Initial release

2017

2014

1990

2008

Current release

5.0.0, May 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

server-less

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

yes

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Source-replica replication

none

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

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

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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.