DBMS > BoltDB vs. Faircom DB vs. Greenplum vs. PostGIS

System Properties Comparison BoltDB vs. Faircom DB vs. Greenplum vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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.

Spatial extension of PostgreSQL

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/boltdb/bolt

www.faircom.com/products/faircom-db

greenplum.org

postgis.net

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.greenplum.org

postgis.net/documentation

Developer

FairCom Corporation

Pivotal Software Inc.

Initial release

2013

1979

2005

Current release

V12, November 2020

7.0.0, September 2023

3.4.2, February 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Restricted, free version available

Open Source

Apache 2.0

Open Source

GPL v2.0

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

ANSI C, C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
Java
Perl
Python
R

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.com

provided by Google News

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

provided by Google News

VMware Greenplum on AWS: Parallel Postgres for Enterprise Analytics at Scale | Amazon Web Services
9 September 2019, AWS Blog

1. Introducing the Greenplum Database - Data Warehousing with Greenplum [Book]
6 December 2018, oreilly.com

Greenplum 6 ventures outside the analytic box | ZDNET
19 March 2019, ZDNet

Greenplum 6 review: Jack of all trades, master of some
7 November 2019, InfoWorld

EMC Introduces Breakthrough 'Big Data' Computing System
13 October 2010, PR Newswire

provided by Google News

Share this page