DBMS > Badger vs. PostGIS vs. XTDB

System Properties Comparison Badger vs. PostGIS vs. XTDB

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.

Spatial extension of PostgreSQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Spatial DBMS

Document store

Secondary database models

Relational DBMS

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

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/dgraph-io/badger

postgis.net

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

postgis.net/documentation

www.xtdb.com/docs

Developer

DGraph Labs

Juxt Ltd.

Initial release

2017

2005

2019

Current release

3.4.2, February 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

MIT License

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

Clojure

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP REST
JDBC

Supported programming languages

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

yes

based on PostgreSQL

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.