DBMS > EJDB vs. Faircom EDGE vs. Google BigQuery vs. Oracle NoSQL vs. SingleStore

System Properties Comparison EJDB vs. Faircom EDGE vs. Google BigQuery vs. Oracle NoSQL vs. SingleStore

Editorial information provided by DB-Engines

Name

Description

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

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 multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Website

github.com/Softmotions/ejdb

www.faircom.com/products/faircom-edge

cloud.google.com/bigquery

www.oracle.com/database/nosql/technologies/nosql

www.singlestore.com

Technical documentation

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

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

cloud.google.com/bigquery/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.singlestore.com

Developer

Softmotions

FairCom Corporation

Google

Oracle

SingleStore Inc.

Initial release

2012

1979

2010

2011

2013

Current release

V3, October 2020

23.3, December 2023

8.5, January 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Restricted, free version available

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

free developer edition available

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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

ANSI C, C++

Java

C++, Go

Server operating systems

server-less

Android
Linux

ARM, x86
Raspbian
Windows

hosted

Linux
Solaris SPARC/x86

Linux

64 bit version required

Data scheme

schema-free

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

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, ANSI Standard SQL Types

yes

optional

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

yes

SQL-like DML and DDL statements

yes

but no triggers and foreign keys

APIs and other access methods

in-process shared library

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

RESTful HTTP/JSON API

RESTful HTTP API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

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

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning

Customizable business rules for partitioning

none

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

across SQL and NoSQL

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

In-memory capabilities

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

yes

off heap cache

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)

Access rights for users and roles

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» more

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.