DBMS > BoltDB vs. Greenplum vs. Microsoft Azure Cosmos DB vs. Tigris

System Properties Comparison BoltDB vs. Greenplum vs. Microsoft Azure Cosmos DB vs. Tigris

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Globally distributed, horizontally scalable, multi-model database service

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

github.com/boltdb/bolt

greenplum.org

azure.microsoft.com/services/cosmos-db

www.tigrisdata.com

Technical documentation

docs.greenplum.org

learn.microsoft.com/azure/cosmos-db

www.tigrisdata.com/docs

Developer

Pivotal Software Inc.

Microsoft

Tigris Data, Inc.

Initial release

2013

2005

2014

2022

Current release

7.0.0, September 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Open Source

Apache Version 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

Linux

hosted

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C
Java
Perl
Python
R

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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

Access rights can be defined down to the item level

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.