DBMS > Badger vs. LeanXcale vs. PostGIS

System Properties Comparison Badger vs. LeanXcale vs. PostGIS

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.

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Spatial extension of PostgreSQL

Primary database model

Key-value store

Key-value store
Relational DBMS

Spatial DBMS

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	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/dgraph-io/badger

www.leanxcale.com

postgis.net

Technical documentation

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

postgis.net/documentation

Developer

DGraph Labs

LeanXcale

Initial release

2017

2015

2005

Current release

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL v2.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

Server operating systems

BSD
Linux
OS X
Solaris
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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

through Apache Derby

yes

APIs and other access methods

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Supported programming languages

C
Java
Scala

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

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

In-memory capabilities

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

yes

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.