DBMS > Atos Standard Common Repository vs. EJDB vs. Google BigQuery vs. HBase

System Properties Comparison Atos Standard Common Repository vs. EJDB vs. Google BigQuery vs. HBase

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

Wide-column store based on Apache Hadoop and on concepts of BigTable

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Wide column store

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Website

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

github.com/Softmotions/ejdb

cloud.google.com/bigquery

hbase.apache.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

hbase.apache.org/book.html

Developer

Atos Convergence Creators

Softmotions

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

2016

2012

2010

2008

Current release

1703

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

Open Source

Apache version 2

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

server-less

hosted

Linux
Unix
Windows

using Cygwin

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free, schema definition possible

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

yes

options to bring your own types, AVRO

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

yes

APIs and other access methods

LDAP

in-process shared library

RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Atomic execution of specific operations

Since BigQuery is designed for querying data

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.