DBMS > Apache Phoenix vs. Atos Standard Common Repository vs. BoltDB vs. Microsoft SQL Server

System Properties Comparison Apache Phoenix vs. Atos Standard Common Repository vs. BoltDB vs. Microsoft SQL Server

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

An embedded key-value store for Go.

Microsofts flagship relational DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Website

phoenix.apache.org

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

github.com/boltdb/bolt

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

Technical documentation

phoenix.apache.org

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

Developer

Apache Software Foundation

Atos Convergence Creators

Microsoft

Initial release

2014

2016

2013

1989

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

1703

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++

Server operating systems

Linux
Unix
Windows

Linux

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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

LDAP

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

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

All languages with LDAP bindings

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

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

LDAP bind authentication

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.