DBMS > Atos Standard Common Repository vs. Coveo vs. EventStoreDB vs. ScyllaDB vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Coveo vs. EventStoreDB vs. ScyllaDB vs. Snowflake

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

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Cassandra and DynamoDB compatible wide column store

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Key-value store

Secondary database models

Key-value store

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

Technical documentation

docs.coveo.com

developers.eventstore.com

docs.scylladb.com

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Coveo

Event Store Limited

ScyllaDB

Snowflake Computing Inc.

Initial release

2016

2012

2015

2014

Current release

1703

21.2, February 2021

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

commercial

Open Source

Open Source (AGPL), commercial license 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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

Java

C++

Server operating systems

Linux

hosted

Linux
Windows

Linux

hosted

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

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

optional

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

Secondary indexes

yes

cluster global secondary indices

SQL

Support of SQL

SQL-like DML and DDL statements (CQL)

yes

APIs and other access methods

LDAP

RESTful HTTP API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C#
Java
JavaScript
Python

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, Lua

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Representation of geographical distribution of servers is possible

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
Tunable Consistency

can be individually decided for each write operation

Immediate 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

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

in-memory tables

User concepts

Access control

LDAP bind authentication

granular access controls, API key management, content filters

Access rights for users can be defined per object

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.