DBMS > Atos Standard Common Repository vs. FoundationDB vs. Microsoft Azure Data Explorer vs. Oracle vs. SiteWhere

System Properties Comparison Atos Standard Common Repository vs. FoundationDB vs. Microsoft Azure Data Explorer vs. Oracle vs. SiteWhere

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Ordered key-value store. Core features are complimented by layers.

Fully managed big data interactive analytics platform

Widely used RDBMS

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Key-value store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

column oriented

Relational DBMS

Time Series DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	5.16
Rank	#69	Overall
	#37	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/apple/foundationdb

azure.microsoft.com/services/data-explorer

www.oracle.com/database

github.com/sitewhere/sitewhere

Technical documentation

apple.github.io/foundationdb

docs.microsoft.com/en-us/azure/data-explorer

docs.oracle.com/en/database

sitewhere1.sitewhere.io/index.html

Developer

Atos Convergence Creators

FoundationDB

Microsoft

Oracle

SiteWhere

Initial release

2016

2013

2019

1980

2010

Current release

1703

6.2.28, November 2020

cloud service with continuous releases

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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

Java

C++

C and C++

Java

Server operating systems

Linux

Linux
OS X
Windows

hosted

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

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

some layers support schemas

Fixed schema with schema-less datatypes (dynamic)

yes

Schemaless in JSON and XML columns

predefined scheme

Typing

predefined data types such as float or date

optional

some layers support typing

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

yes

SQL

Support of SQL

supported in specific SQL layer only

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

LDAP

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

Server-side scripts

Stored procedures

in SQL-layer only

Yes, possible languages: KQL, Python, R

PL/SQL

also stored procedures in Java possible

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Linearizable consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

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

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

User concepts

Access control

LDAP bind authentication

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.