DBMS > BoltDB vs. GeoSpock vs. Greenplum vs. RocksDB

System Properties Comparison BoltDB vs. GeoSpock vs. Greenplum vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

An embedded key-value store for Go.

Spatial and temporal data processing engine for extreme data scale

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

Primary database model

Key-value store

Relational DBMS

Key-value store

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	9.23
Rank	#47	Overall
	#30	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

geospock.com

greenplum.org

rocksdb.org

Technical documentation

docs.greenplum.org

github.com/facebook/rocksdb/wiki

Developer

GeoSpock

Pivotal Software Inc.

Facebook, Inc.

Initial release

2013

2005

2013

Current release

2.0, September 2019

7.0.0, September 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

Open Source

BSD

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

Java, Javascript

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

schema-free

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

since Version 4.2

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

JDBC
ODBC

C++ API
Java API

Supported programming languages

C
Java
Perl
Python
R

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

ACID

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.

yes

User concepts

Access control

Access rights for users can be defined per table

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.