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

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

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

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

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

A fully ACID in-memory object graph database

Primary database model

Document store
Key-value store

Spatial DBMS

Search engine

Document store
Object oriented DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

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

www.geomesa.org

manticoresearch.com

origodb.com

Technical documentation

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

manual.manticoresearch.com

origodb.com/docs

Developer

Atos Convergence Creators

CCRi and others

Manticore Software

Robert Friberg et al

Initial release

2016

2014

2017

2009

under the name LiveDB

Current release

1703

5.0.1, July 2024

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPL version 2

Open Source

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++

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Fixed schema

yes

Typing

predefined data types such as float or date

optional

yes

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

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

LDAP

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

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages with LDAP bindings

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

.Net

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

depending on storage layer

Sharding

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

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

Synchronous replication based on Galera library

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

depending on storage layer

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

Atomic execution of specific operations

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

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.

yes

Write ahead log

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

Role based authorization

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

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

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

Highlighting in Search Results
24 May 2020, hackernoon.com

40 Stories To Learn About Elasticsearch
27 April 2023, hackernoon.com

Optimizing Elastic Search for High-Load Applications
18 August 2023, hackernoon.com

provided by Google News

Share this page