DBMS > Faircom DB vs. Faircom EDGE vs. Google Cloud Firestore vs. Ignite vs. SQLite

System Properties Comparison Faircom DB vs. Faircom EDGE vs. Google Cloud Firestore vs. Ignite vs. SQLite

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.

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.faircom.com/products/faircom-edge

firebase.google.com/products/firestore

ignite.apache.org

www.sqlite.org

Technical documentation

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

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

firebase.google.com/docs/firestore

apacheignite.readme.io/docs

www.sqlite.org/docs.html

Developer

FairCom Corporation

Google

Apache Software Foundation

Dwayne Richard Hipp

Initial release

1979

2017

2015

2000

Current release

V12, November 2020

V3, October 2020

Apache Ignite 2.6

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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++

C++, Java, .Net

Server operating systems

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

easily portable to other OSs

Android
Linux

ARM, x86
Raspbian
Windows

hosted

Linux
OS X
Solaris
Windows

server-less

Data scheme

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

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

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes, ANSI Standard SQL Types

yes

not rigid because of 'dynamic typing' concept.

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 with proprietary extensions

yes

ANSI SQL queries

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

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

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

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

.Net, JavaScript, C/C++

yes, Firebase Rules & Cloud Functions

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes, with Cloud Functions

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency
Tunable Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

via file-system locks

Durability

Support for making data persistent

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 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. Security Rules for 3rd party authentication using Firebase Auth.

Security Hooks for custom implementations

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.