DBMS > Atos Standard Common Repository vs. GigaSpaces vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Oracle Berkeley DB

System Properties Comparison Atos Standard Common Repository vs. GigaSpaces vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

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

Description

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Microsofts flagship relational DBMS

Widely used in-process key-value store

Primary database model

Document store
Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Document store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Graph DBMS
Search engine

Document store
Graph DBMS
Spatial DBMS

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

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

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

www.gigaspaces.com

cloud.google.com/datastore

www.microsoft.com/en-us/sql-server

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

Technical documentation

docs.gigaspaces.com/latest/landing.html

cloud.google.com/datastore/docs

learn.microsoft.com/en-US/sql/sql-server

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

Developer

Atos Convergence Creators

Gigaspaces Technologies

Google

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2000

2008

1989

1994

Current release

1703

15.5, September 2020

SQL Server 2022, November 2022

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

commercial

restricted free version is available

Open Source

commercial license 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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

Java, C++, .Net

C++

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

Server operating systems

Linux

Linux
macOS
Solaris
Windows

hosted

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

yes, details here

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

XML can be used for describing objects metadata

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

SQL-like query language (GQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

LDAP

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

All languages with LDAP bindings

.Net
C++
Java
Python
Scala

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
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

using Google App Engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

yes, event driven architecture

Callbacks using the Google Apps Engine

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

User concepts

Access control

LDAP bind authentication

Role-based access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.