DBMS > Faircom EDGE vs. Google BigQuery vs. jBASE vs. PlanetScale

System Properties Comparison Faircom EDGE vs. Google BigQuery vs. jBASE vs. PlanetScale

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 robust multi-value DBMS comprising development tools and middleware

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

www.faircom.com/products/faircom-edge

cloud.google.com/bigquery

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

planetscale.com

Technical documentation

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

cloud.google.com/bigquery/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

planetscale.com/docs

Developer

FairCom Corporation

Google

Rocket Software (formerly Zumasys)

PlanetScale

Initial release

1979

2010

1991

2020

Current release

V3, October 2020

5.7

License

Commercial or Open Source

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

Android
Linux

ARM, x86
Raspbian
Windows

hosted

AIX
Linux
Windows

Docker
Linux
macOS

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

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

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

when using SQL

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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 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 can be defined down to the item level

Users with fine-grained authorization concept

no user groups or roles

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.