DBMS > Atos Standard Common Repository vs. Cubrid vs. GeoMesa vs. Manticore Search

System Properties Comparison Atos Standard Common Repository vs. Cubrid vs. GeoMesa vs. Manticore Search

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.

Multi-storage database for search, including full-text search.

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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	0.22
Rank	#312	Overall
	#21	Search engines

Website

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

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

www.geomesa.org

manticoresearch.com

Technical documentation

cubrid.org/manuals

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

manual.manticoresearch.com

Developer

Atos Convergence Creators

CUBRID Corporation, CUBRID Foundation

CCRi and others

Manticore Software

Initial release

2016

2008

2014

2017

Current release

1703

11.0, January 2021

4.0.5, February 2024

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

GPL version 2

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

FreeBSD
Linux
macOS
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Fixed schema

Typing

predefined data types such as float or date

optional

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
OLE DB

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

All languages with LDAP bindings

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

depending on storage layer

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

depending on storage layer

Synchronous replication based on Galera library

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

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

depending on storage layer

User concepts

Access control

LDAP bind authentication

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

Google's Gemini comes to databases
9 April 2024, Yahoo Canada Shine On

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

provided by Google News

Share this page