DBMS > Atos Standard Common Repository vs. Drizzle vs. Microsoft SQL Server vs. OrigoDB vs. SwayDB

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. Microsoft SQL Server vs. OrigoDB vs. SwayDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Microsofts flagship relational DBMS

A fully ACID in-memory object graph database

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	0.04
Rank	#373	Overall
	#57	Key-value stores

Website

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

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

origodb.com

swaydb.simer.au

Technical documentation

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

origodb.com/docs

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Microsoft

Robert Friberg et al

Simer Plaha

Initial release

2016

2008

1989

2009

under the name LiveDB

2018

Current release

1703

7.2.4, September 2012

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

restricted free version is available

Open Source

GNU Affero GPL V3.0

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

C++

Scala

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

User defined using .NET types and collections

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 be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

JDBC

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

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

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

.Net

Java
Kotlin
Scala

Server-side scripts

Stored procedures

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

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

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

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Source-replica replication

none

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

depending on model

Transaction concepts

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

Atomic execution of specific operations

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Role based authorization

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.