DBMS > Atos Standard Common Repository vs. Coveo vs. Geode vs. XTDB

System Properties Comparison Atos Standard Common Repository vs. Coveo vs. Geode vs. XTDB

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Key-value store

Search engine

Key-value store

Document store

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

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

www.coveo.com

geode.apache.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.coveo.com

geode.apache.org/docs

www.xtdb.com/docs

Developer

Atos Convergence Creators

Coveo

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Juxt Ltd.

Initial release

2016

2012

2002

2019

Current release

1703

1.1, February 2017

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

MIT License

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.

Implementation language

Java

Clojure

Server operating systems

Linux

hosted

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Schema and schema-less with LDAP views

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

Typing

predefined data types such as float or date

optional

yes

yes, extensible-data-notation format

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

LDAP

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
JDBC

Supported programming languages

All languages with LDAP bindings

C#
Java
JavaScript
Python

.Net
All JVM based languages
C++
Groovy
Java
Scala

Clojure
Java

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

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes, each node contains all data

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

Transaction concepts

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

Atomic execution of specific operations

yes

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

granular access controls, API key management, content filters

Access rights per client and object definable

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

Coveo announced its joining in the MACH Alliance
26 April 2024, Martechcube

AI for CX: Coveo's award-winning solution
17 April 2024, CMSWire

Coveo joins MACH Alliance to advocate open tech ecosystem
29 April 2024, IT Brief Australia

Coveo to Showcase the Significant Impact of AI and GenAI to Improve Digital Experiences at 10th Edition of Relevance ...
21 March 2024, GlobeNewswire

How Coveo delivers better experiences with generative AI by partnering with CIOs
20 October 2023, Fast Company

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page