DBMS > Atos Standard Common Repository vs. Manticore Search vs. MySQL vs. Rockset

System Properties Comparison Atos Standard Common Repository vs. Manticore Search vs. MySQL vs. Rockset

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.

Widely used open source RDBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Document store
Key-value store

Search engine

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

Relational DBMS
Search engine

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

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

manticoresearch.com

www.mysql.com

rockset.com

Technical documentation

manual.manticoresearch.com

dev.mysql.com/doc

docs.rockset.com

Developer

Atos Convergence Creators

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Initial release

2016

2017

1995

2019

Current release

1703

6.0, February 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

optional

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

yes

dynamic typing

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

yes

ingestion from XML files supported

Secondary indexes

yes

full-text index on all search fields

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

Read-only SQL queries, including JOINs

APIs and other access methods

LDAP

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

All languages with LDAP bindings

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and organizations can be defined via Rockset console

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.