DBMS > Badger vs. Google Cloud Datastore vs. PostGIS vs. TimescaleDB

System Properties Comparison Badger vs. Google Cloud Datastore vs. PostGIS vs. TimescaleDB

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Spatial extension of PostgreSQL

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

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	4.49
Rank	#79	Overall
	#12	Document stores

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.87
Rank	#74	Overall
	#4	Time Series DBMS

Website

github.com/dgraph-io/badger

cloud.google.com/datastore

postgis.net

www.timescale.com

Technical documentation

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

cloud.google.com/datastore/docs

postgis.net/documentation

docs.timescale.com

Developer

DGraph Labs

Google

Timescale

Initial release

2017

2008

2005

2017

Current release

3.4.2, February 2024

2.13.0, November 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL v2.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

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

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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 query language (GQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

based on PostgreSQL

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

based on PostgreSQL

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.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Best cloud storage of 2024
3 April 2024, TechRadar

What Is Google Cloud Platform?
28 August 2023, Simplilearn

Compare Google Cloud Storage vs. Google Drive for enterprises
9 November 2023, TechTarget

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Visualizing IoT Data at Scale With Hopara and TimescaleDB
16 May 2023, Embedded Computing Design

Timescale Announces Corporate Rebrand Reflecting Company's Growth
17 May 2023, PR Newswire

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

provided by Google News

Share this page