DBMS > Atos Standard Common Repository vs. CrateDB vs. Qdrant vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. CrateDB vs. Qdrant vs. Snowflake

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

Distributed Database based on Lucene

A high-performance vector database with neural network or semantic-based matching

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

Primary database model

Document store
Key-value store

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.71
Rank	#227	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#10	Vector DBMS

Score	1.28
Rank	#167	Overall
	#8	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

cratedb.com

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

cratedb.com/docs

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Crate

Qdrant

Snowflake Computing Inc.

Initial release

2016

2013

2021

2014

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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.

Implementation language

Java

Rust

Server operating systems

Linux

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Docker
Linux
macOS
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

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

Typing

predefined data types such as float or date

optional

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions (Javascript)

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

Collection-level 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

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency, tunable consistency

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

User concepts

Access control

LDAP bind authentication

rights management via user accounts

Key-based authentication

Users with fine-grained authorization concept, user roles and pluggable 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.