DBMS > Atos Standard Common Repository vs. Cubrid vs. GeoMesa vs. MarkLogic

System Properties Comparison Atos Standard Common Repository vs. Cubrid vs. GeoMesa vs. MarkLogic

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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

Operational and transactional Enterprise NoSQL database

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Website

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

cubrid.com (korean)
cubrid.org (english)

www.geomesa.org

www.marklogic.com

Technical documentation

cubrid.org/manuals

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

docs.marklogic.com

Developer

Atos Convergence Creators

CUBRID Corporation, CUBRID Foundation

CCRi and others

MarkLogic Corp.

Initial release

2016

2008

2014

2001

Current release

1703

11.0, January 2021

4.0.5, February 2024

11.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

commercial

restricted free version is available

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, C++, Java

Scala

C++

Server operating systems

Linux

Linux
Windows

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Schema can be enforced

Typing

predefined data types such as float or date

optional

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

yes

SQL92

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
OLE DB

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Supported programming languages

All languages with LDAP bindings

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via XQuery or JavaScript

Triggers

yes

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

Source-replica replication

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

can act as a resource manager in an XA/JTA transaction

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

depending on storage layer

yes, with Range Indexes

User concepts

Access control

LDAP bind authentication

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

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

Progress (PRGS) Set to Buy MarkLogic, Guides Upbeat Q4 Results
16 May 2024, Yahoo Lifestyle Australia

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
22 April 2024, Medium

Database Platform to Simplify Complex Data | Progress Marklogic
7 February 2023, Progress Software

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, GlobeNewswire

AI can make logistics data as valuable as intelligence or operational data for mission success
17 April 2024, Breaking Defense

provided by Google News

Share this page