DBMS > Google Cloud Bigtable vs. Lovefield vs. PostGIS vs. RocksDB vs. Splunk

System Properties Comparison Google Cloud Bigtable vs. Lovefield vs. PostGIS vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Embeddable relational database for web apps written in pure JavaScript

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Analytics Platform for Big Data

Primary database model

Key-value store
Wide column store

Secondary database models

Relational DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

cloud.google.com/bigtable

google.github.io/lovefield

postgis.net

rocksdb.org

www.splunk.com

Technical documentation

cloud.google.com/bigtable/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

postgis.net/documentation

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Google

Facebook, Inc.

Splunk Inc.

Initial release

2015

2014

2005

2013

2003

Current release

2.1.12, February 2017

3.4.2, February 2024

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

JavaScript

C++

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

SQL-like query language

via JavaScript builder pattern

yes

Splunk Search Processing Language for search commands

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

C++ API
Java API

HTTP REST

Supported programming languages

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

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

based on PostgreSQL

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

none

yes

based on PostgreSQL

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

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

yes

based on PostgreSQL

Access rights for users and 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.