DBMS > Badger vs. Oracle NoSQL vs. PostGIS vs. Vitess

System Properties Comparison Badger vs. Oracle NoSQL vs. PostGIS vs. Vitess

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 multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Spatial extension of PostgreSQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store

Document store
Key-value store
Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

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

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

github.com/dgraph-io/badger

www.oracle.com/database/nosql/technologies/nosql

postgis.net

vitess.io

Technical documentation

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

postgis.net/documentation

vitess.io/docs

Developer

DGraph Labs

Oracle

The Linux Foundation, PlanetScale

Initial release

2017

2011

2005

2013

Current release

24.1, May 2024

3.4.2, February 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

GPL v2.0

Open Source

Apache Version 2.0, commercial licenses available

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

Docker
Linux
macOS

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

optional

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

based on PostgreSQL

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

configurable

ACID within a storage node (=shard)

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

off heap cache

yes

User concepts

Access control

Access rights for users and roles

yes

based on PostgreSQL

Users with fine-grained authorization concept

no user groups or roles

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.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

OpenWorld 2013: Oracle NoSQL Database On the Rise?
13 December 2023, Channel Futures

Blog Theme - Details
21 August 2023, Oracle

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, Oracle

Oracle NoSQL database comes to the cloud
2 April 2020, TechTarget

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page