DBMS > EJDB vs. Faircom DB vs. Google Cloud Bigtable

System Properties Comparison EJDB vs. Faircom DB vs. Google Cloud Bigtable

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Primary database model

Document store

Key-value store
Relational DBMS

Key-value store
Wide column store

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Website

github.com/Softmotions/ejdb

www.faircom.com/products/faircom-db

cloud.google.com/bigtable

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

cloud.google.com/bigtable/docs

Developer

Softmotions

FairCom Corporation

Google

Initial release

2012

1979

2015

Current release

V12, November 2020

License

Commercial or Open Source

Open Source

GPLv2

commercial

Restricted, free version available

commercial

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

Server operating systems

server-less

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

easily portable to other OSs

hosted

Data scheme

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, ANSI SQL Types, JSON, typed binary structures

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.

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

APIs and other access methods

in-process shared library

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

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

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).

Internal replication in Colossus, and regional replication between two clusters in different zones

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

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

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

Recent citations in the news

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

provided by Google News

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

What is Google Bigtable? | Definition from TechTarget
1 March 2022, TechTarget

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

provided by Google News

Share this page