DBMS > Atos Standard Common Repository vs. Manticore Search vs. OpenSearch

System Properties Comparison Atos Standard Common Repository vs. Manticore Search vs. OpenSearch

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

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Document store
Key-value store

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	0.28
Rank	#310	Overall
	#22	Search engines

Score	10.44
Rank	#48	Overall
	#4	Search engines

Website

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

manticoresearch.com

github.com/opensearch-project
opensearch.org

Technical documentation

manual.manticoresearch.com

opensearch.org/docs/latest

Developer

Atos Convergence Creators

Manticore Software

Amazon Web Services

Initial release

2016

2017

2021

Current release

1703

4.2, December 2021

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

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

Aiven for OpenSearch: Fully managed open source search and analytics suite including search engine, NoSQL document database, and visualization interface.

Implementation language

Java

C++

Java

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

All OS with a Java VM

Data scheme

Schema and schema-less with LDAP views

Fixed schema

schema-free

Flexible type definitions. Once a type is defined, it is persistent

Typing

predefined data types such as float or date

optional

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

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

All search fields are automatically indexed

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

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

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

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

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

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.