DBMS > Faircom EDGE vs. GridDB vs. NuoDB vs. Oracle vs. Oracle Berkeley DB

System Properties Comparison Faircom EDGE vs. GridDB vs. NuoDB vs. Oracle vs. Oracle Berkeley DB

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

Scalable in-memory time series database optimized for IoT and Big Data

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Widely used RDBMS

Widely used in-process key-value store

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Key-value store
Relational DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.03
Rank	#380	Overall
	#59	Key-value stores
	#157	Relational DBMS

Score	2.02
Rank	#132	Overall
	#11	Time Series DBMS

Score	0.99
Rank	#195	Overall
	#92	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

www.faircom.com/products/faircom-edge

griddb.net

www.3ds.com/nuodb-distributed-sql-database

www.oracle.com/database

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

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

docs.griddb.net

doc.nuodb.com

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

Developer

FairCom Corporation

Toshiba Corporation

Dassault Systèmes

originally NuoDB, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

1979

2013

1980

1994

Current release

V3, October 2020

5.1, August 2022

23c, September 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

limited edition free

commercial

restricted free version is available

Open Source

commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

C++

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

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

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

numerical, string, blob, geometry, boolean, timestamp

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

SQL92, SQL-like TQL (Toshiba Query Language)

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Java, SQL

PL/SQL

also stored procedures in Java possible

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

data is dynamically stored/cached on the nodes where it is read/written

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

yes

Managed transparently by NuoDB

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

ACID at container level

ACID

tunable commit protocol

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

MVCC

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

Temporary table

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Access rights for users can be defined per database

Standard SQL roles/ privileges, Administrative Users

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.