DBMS > Atos Standard Common Repository vs. BigchainDB vs. Dgraph vs. Manticore Search vs. Microsoft SQL Server

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Dgraph vs. Manticore Search vs. Microsoft SQL Server

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

Distributed and scalable native Graph DBMS

Multi-storage database for search, including full-text search.

Microsofts flagship relational DBMS

Primary database model

Document store
Key-value store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	0.23
Rank	#317	Overall
	#21	Search engines

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

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

www.bigchaindb.com

dgraph.io

manticoresearch.com

www.microsoft.com/en-us/sql-server

Technical documentation

bigchaindb.readthedocs.io/en/latest

dgraph.io/docs

manual.manticoresearch.com

learn.microsoft.com/en-US/sql/sql-server

Developer

Atos Convergence Creators

Dgraph Labs, Inc.

Manticore Software

Microsoft

Initial release

2016

2017

1989

Current release

1703

6.0, February 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache 2.0

Open Source

GPL version 2

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

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

Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

optional

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, 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

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Synchronous replication via Raft

Synchronous replication based on Galera library

yes, but depending on the SQL-Server Edition

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

The original contents of fields are not stored in the Manticore index.

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

Planned for future releases

fine grained access rights according to SQL-standard

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.