DBMS > BoltDB vs. Faircom EDGE vs. Google Cloud Datastore vs. HBase vs. RocksDB

System Properties Comparison BoltDB vs. Faircom EDGE vs. Google Cloud Datastore vs. HBase vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Primary database model

Key-value store

Key-value store
Relational DBMS

Document store

Wide column store

Key-value store

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

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

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

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

Website

github.com/boltdb/bolt

www.faircom.com/products/faircom-edge

cloud.google.com/datastore

hbase.apache.org

rocksdb.org

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

cloud.google.com/datastore/docs

hbase.apache.org/book.html

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Facebook, Inc.

Initial release

2013

1979

2008

2013

Current release

V3, October 2020

2.3.4, January 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Restricted, free version available

commercial

Open Source

Apache version 2

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

ANSI C, C++

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
Linux

ARM, x86
Raspbian
Windows

hosted

Linux
Unix
Windows

using Cygwin

Linux

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes, details here

options to bring your own types, AVRO

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

yes

ANSI SQL queries

SQL-like query language (GQL)

APIs and other access methods

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

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

Java API
RESTful HTTP API
Thrift

C++ API
Java API

Supported programming languages

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

using Google App Engine

yes

Coprocessors in Java

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning

Customizable business rules for partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency
Tunable Consistency

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 or Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Single row ACID (across millions of columns)

yes

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.