DBMS > Atos Standard Common Repository vs. Badger vs. Google Cloud Datastore vs. HyperSQL

System Properties Comparison Atos Standard Common Repository vs. Badger vs. Google Cloud Datastore vs. HyperSQL

Please select another system to include it in the comparison.

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

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Primary database model

Document store
Key-value store

Key-value store

Document store

Relational DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

Website

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

github.com/dgraph-io/badger

cloud.google.com/datastore

hsqldb.org

Technical documentation

godoc.org/github.com/dgraph-io/badger

cloud.google.com/datastore/docs

hsqldb.org/web/hsqlDocsFrame.html

Developer

Atos Convergence Creators

DGraph Labs

Google

Initial release

2016

2017

2008

2001

Current release

1703

2.7.2, June 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

based on BSD license

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

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

hosted

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

LDAP

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

HTTP API

JDBC via HTTP
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

All languages supporting JDBC/ODBC
Java

Server-side scripts

Stored procedures

using Google App Engine

Java, SQL

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

none

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Best cloud storage of 2024
4 June 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Introduction to JDBC with HSQLDB tutorial
14 November 2022, TheServerSide.com

HyperSQL DataBase flaw leaves library vulnerable to RCE
24 October 2022, The Daily Swig

provided by Google News

Share this page