DBMS > Apache Doris vs. Atos Standard Common Repository vs. RocksDB vs. SAP HANA

System Properties Comparison Apache Doris vs. Atos Standard Common Repository vs. RocksDB vs. SAP HANA

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

An MPP-based analytics DBMS embracing the MySQL protocol

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

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

rocksdb.org

www.sap.com/products/hana.html

Technical documentation

github.com/apache/doris/wiki

github.com/facebook/rocksdb/wiki

help.sap.com/hana

Developer

Apache Software Foundation, originally contributed from Baidu

Atos Convergence Creators

Facebook, Inc.

SAP

Initial release

2017

2016

2013

2010

Current release

1.2.2, February 2023

1703

9.2.1, May 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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

Appliance or cloud-service

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

yes

APIs and other access methods

JDBC
MySQL client

LDAP

C++ API
Java API

JDBC
ODBC

Supported programming languages

Java

All languages with LDAP bindings

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

cell division

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

fine grained access rights according to SQL-standard

LDAP bind authentication

yes

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.