DBMS > Faircom EDGE vs. Google BigQuery vs. Hazelcast vs. PouchDB

System Properties Comparison Faircom EDGE vs. Google BigQuery vs. Hazelcast vs. PouchDB

Please select another system to include it in the comparison.

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

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

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

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

www.faircom.com/products/faircom-edge

cloud.google.com/bigquery

hazelcast.com

pouchdb.com

Technical documentation

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

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

pouchdb.com/guides

Developer

FairCom Corporation

Google

Hazelcast

Apache Software Foundation

Initial release

1979

2010

2008

2012

Current release

V3, October 2020

5.3.6, November 2023

7.1.1, June 2019

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

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

JavaScript

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

hosted

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

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

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

via views

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL-like query language

APIs and other access methods

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

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

View functions in JavaScript

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

Replicated Map

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

one or two-phase-commit; repeatable reads; read commited

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control

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.