DBMS > Atos Standard Common Repository vs. BigchainDB vs. dBASE vs. Snowflake vs. YTsaurus

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. dBASE vs. Snowflake vs. YTsaurus

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

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

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Document store
Key-value store

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#340	Overall
	#45	Document stores
	#50	Key-value stores

Website

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

docs.snowflake.net/manuals/index.html

ytsaurus.tech/docs/en

Developer

Atos Convergence Creators

Asthon Tate

Snowflake Computing Inc.

Yandex

Initial release

2016

1979

2014

2023

Current release

1703

dBASE 2019, 2019

License

Commercial or Open Source

commercial

Open Source

AGPL v3

commercial

Open Source

Apache License, Version 2.0

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

Python

C++

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

hosted

Ubuntu

Data scheme

Schema and schema-less with LDAP views

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

SQL

Support of SQL

yes

YQL, an SQL-based language, is supported

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

JavaScript (Node.js)
Python

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

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

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

yes

Access rights for users and roles

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

Access Control Lists

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.