DBMS > Faircom EDGE vs. Google BigQuery vs. Memcached vs. Rockset

System Properties Comparison Faircom EDGE vs. Google BigQuery vs. Memcached vs. Rockset

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

In-memory key-value store, originally intended for caching

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Document store

Secondary database models

Relational DBMS
Search engine

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

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

www.faircom.com/products/faircom-edge

cloud.google.com/bigquery

www.memcached.org

rockset.com

Technical documentation

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

cloud.google.com/bigquery/docs

github.com/memcached/memcached/wiki

docs.rockset.com

Developer

FairCom Corporation

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Rockset

Initial release

1979

2010

2003

2019

Current release

V3, October 2020

1.6.27, May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

BSD license

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

C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

hosted

FreeBSD
Linux
OS X
Unix
Windows

hosted

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

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

ANSI SQL queries

yes

Read-only SQL queries, including JOINs

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

Proprietary protocol

HTTP REST

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

Repcached, a Memcached patch, provides this functionallity

yes

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

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

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

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)

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights for users and organizations can be defined via Rockset console

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.