DBMS > Atos Standard Common Repository vs. Postgres-XL vs. Qdrant vs. SQLite

System Properties Comparison Atos Standard Common Repository vs. Postgres-XL vs. Qdrant vs. SQLite

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

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

A high-performance vector database with neural network or semantic-based matching

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	1.28
Rank	#167	Overall
	#8	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.postgres-xl.org

github.com/qdrant/qdrant
qdrant.tech

www.sqlite.org

Technical documentation

www.postgres-xl.org/documentation

qdrant.tech/documentation

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Qdrant

Dwayne Richard Hipp

Initial release

2016

2014

since 2012, originally named StormDB

2021

2000

Current release

1703

10 R1, October 2018

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Rust

Server operating systems

Linux

Linux
macOS

Docker
Linux
macOS
Windows

server-less

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

Numbers, Strings, Geo, Boolean

yes

not rigid because of 'dynamic typing' concept.

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

XML type, but no XML query functionality

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Collection-level 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

Eventual Consistency, tunable 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

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

LDAP bind authentication

fine grained access rights according to SQL-standard

Key-based authentication

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.