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

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

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 fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

Search engine

Document store
Object oriented DBMS

Relational 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.29
Rank	#302	Overall
	#21	Search engines

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

manticoresearch.com

origodb.com

www.sqlite.org

Technical documentation

manual.manticoresearch.com

origodb.com/docs

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Manticore Software

Robert Friberg et al

Dwayne Richard Hipp

Initial release

2016

2017

2009

under the name LiveDB

2000

Current release

1703

6.0, February 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Public Domain

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

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

Linux
Windows

server-less

Data scheme

Schema and schema-less with LDAP views

Fixed schema

yes

dynamic column types

Typing

predefined data types such as float or date

optional

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

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-92 is not fully supported

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

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

.Net

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Domain Events

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

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

Source-replica replication

none

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

Foreign keys

Referential integrity

depending on model

yes

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

via file-system locks

Durability

Support for making data persistent

yes

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

yes

Write ahead log

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

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.