DBMS > Atos Standard Common Repository vs. EJDB vs. GeoMesa vs. Ignite

System Properties Comparison Atos Standard Common Repository vs. EJDB vs. GeoMesa vs. Ignite

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)

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Document store
Key-value store

Document store

Spatial DBMS

Key-value store
Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

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

github.com/Softmotions/ejdb

www.geomesa.org

ignite.apache.org

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

apacheignite.readme.io/docs

Developer

Atos Convergence Creators

Softmotions

CCRi and others

Apache Software Foundation

Initial release

2016

2012

2014

2015

Current release

1703

4.0.5, February 2024

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

Apache 2.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

Scala

C++, Java, .Net

Server operating systems

Linux

server-less

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

LDAP

in-process shared library

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

depending on storage layer

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Immediate 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

ACID

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

depending on storage layer

yes

User concepts

Access control

LDAP bind authentication

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

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

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: An Overview
6 September 2023, Open Source For You

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page