DBMS > Badger vs. Transbase

System Properties Comparison Badger vs. Transbase

Please select another system to include it in the comparison.

Our visitors often compare Badger and Transbase with SQLite, etcd and PostgreSQL.

Editorial information provided by DB-Engines

Name

Description

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Key-value store

Relational DBMS

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

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

github.com/dgraph-io/badger

www.transaction.de/en/products/transbase.html

Technical documentation

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

www.transaction.de/en/products/transbase/features.html

Developer

DGraph Labs

Transaction Software GmbH

Initial release

2017

1987

Current release

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free development 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

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

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

yes

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.

User concepts

Access control

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.

Share this page