DBMS > BigchainDB vs. Faircom EDGE vs. FatDB vs. GeoMesa

System Properties Comparison BigchainDB vs. Faircom EDGE vs. FatDB vs. GeoMesa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Primary database model

Document store

Key-value store
Relational DBMS

Document store
Key-value store

Spatial DBMS

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	0.02
Rank	#370	Overall
	#55	Key-value stores
	#157	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Website

www.bigchaindb.com

www.faircom.com/products/faircom-edge

www.geomesa.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

www.geomesa.org/documentation/stable/user/index.html

Developer

FairCom Corporation

FatCloud

CCRi and others

Initial release

2016

1979

2012

2014

Current release

V3, October 2020

5.0.1, July 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Restricted, free version available

commercial

Open Source

Apache License 2.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

Python

ANSI C, C++

Scala

Server operating systems

Linux

Android
Linux

ARM, x86
Raspbian
Windows

Windows

Data scheme

schema-free

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

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL 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

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

Via inetgration in SQL Server

APIs and other access methods

CLI Client
RESTful HTTP API

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Eventual Consistency
Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

when using SQL

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

yes

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

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

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

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

Blockchain Database Startup BigchainDB Raises €3 Million
27 September 2016, CoinDesk

7 blockchain firms join Bosch led GAIA-X consortium for vehicle identity
13 September 2022, Ledger Insights

How to use blockchain to build a database solution
2 March 2017, ZDNet

BigchainDB: A Popular and Powerful Database for Blockchain
9 September 2019, Open Source For You

provided by Google News

Data Technology Company FairCom Expands The Edge with 2 New Releases of its Edge Computing Products
19 April 2023, businesswire.com

Brokers, Protocols, Platform Move Manufacturing Data
26 July 2023, EE Times

Winners of the 2021 IoT Evolution Product of the Year Awards Announced
6 July 2021, IoT Evolution World

How To Collect, Store, and Query IoT Data With MQTT + SQL
16 June 2022, IoT For All

Trend-Setting Products in Data and Information Management for 2023
8 December 2022, Database Trends and Applications

provided by Google News

Share this page