DBMS > Atos Standard Common Repository vs. EJDB vs. HBase vs. JaguarDB

System Properties Comparison Atos Standard Common Repository vs. EJDB vs. HBase vs. JaguarDB

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)

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

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Document store
Key-value store

Document store

Wide column store

Key-value store
Vector DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Website

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

github.com/Softmotions/ejdb

hbase.apache.org

www.jaguardb.com

Technical documentation

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

hbase.apache.org/book.html

www.jaguardb.com/support.html

Developer

Atos Convergence Creators

Softmotions

Apache Software Foundation

Apache top-level project, originally developed by Powerset

DataJaguar, Inc.

Initial release

2016

2012

2008

2015

Current release

1703

2.3.4, January 2021

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache version 2

Open Source

GPL V3.0

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

Java

C++

the server part. Clients available in other languages

Server operating systems

Linux

server-less

Linux
Unix
Windows

using Cygwin

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

options to bring your own types, AVRO

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

LDAP

in-process shared library

Java API
RESTful HTTP API
Thrift

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Server-side scripts

Stored procedures

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

Multi-source 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 or Eventual Consistency

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

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

rights management via user accounts

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

DB-Engines blog posts

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

Why is Hadoop not listed in the DB-Engines Ranking?
13 May 2013, Paul Andlinger

show all

Recent citations in the news

Best Practices from Rackspace for Modernizing a Legacy HBase/Solr Architecture Using AWS Services | Amazon Web ...
9 October 2023, AWS Blog

Less Components, Higher Performance: Apache Doris instead of ClickHouse, MySQL, Presto, and HBase
20 October 2023, hackernoon.com

HBase: The database big data left behind
6 May 2016, InfoWorld

What Is HBase? (Definition, Uses, Benefits, Features)
22 December 2022, Built In

HBase Tutorial
24 February 2023, Simplilearn

provided by Google News

Share this page