DBMS > Atos Standard Common Repository vs. Ehcache vs. Manticore Search vs. Ultipa

System Properties Comparison Atos Standard Common Repository vs. Ehcache vs. Manticore Search vs. Ultipa

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

A widely adopted Java cache with tiered storage options

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

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Document store
Key-value store

Key-value store

Search engine

Graph 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	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.13
Rank	#335	Overall
	#31	Graph DBMS

Website

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

www.ehcache.org

manticoresearch.com

www.ultipa.com

Technical documentation

www.ehcache.org/documentation

manual.manticoresearch.com

www.ultipa.com/document

Developer

Atos Convergence Creators

Terracotta Inc, owned by Software AG

Manticore Software

Ultipa

Initial release

2016

2009

2017

2019

Current release

1703

3.10.0, March 2022

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2

commercial

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

All OS with a Java VM

FreeBSD
Linux
macOS
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

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

SQL-like query language

APIs and other access methods

LDAP

JCache

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

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

Java

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

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Synchronous replication based on Galera library

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

Tunable Consistency (Strong, Eventual, Weak)

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes

supports JTA and can work as an XA resource

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

using a tiered cache-storage approach

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Jira Data Center user? Here's a critical Ehcache vulnerability to spoil your day
22 July 2021, The Register

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

Migration From JBoss 5 to JBoss 7: All It Takes Is 11 Easy Steps
3 June 2021, hackernoon.com

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

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

US’ Ultipa expands African footprint
6 March 2024, Caj News Africa

Technology
7 March 2024, Caj News Africa

provided by Google News

Share this page