DBMS > Atos Standard Common Repository vs. IBM Db2 warehouse vs. JaguarDB vs. JSqlDb vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. IBM Db2 warehouse vs. JaguarDB vs. JSqlDb vs. Snowflake

Editorial information provided by DB-Engines

Name

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

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

Cloud-based data warehousing service

Performant, highly scalable DBMS for AI and IoT applications

JavaScript Query Language Database, stores JavaScript objects and primitives

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

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Vector DBMS

Document store
Object oriented DBMS

Relational DBMS

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

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.ibm.com/products/db2/warehouse

www.jaguardb.com

jsqldb.org (offline)

www.snowflake.com

Technical documentation

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

IBM

DataJaguar, Inc.

Konrad von Backstrom

Snowflake Computing Inc.

Initial release

2016

2014

2015

2018

2014

Current release

1703

3.3 July 2023

0.8, December 2018

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

commercial

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

C++

the server part. Clients available in other languages

Server operating systems

Linux

hosted

Linux

Linux
macOS
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

yes

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

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

LDAP

.NET Client API
JDBC
ODBC
OLE DB

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

PL/SQL, SQL PL

functions in JavaScript

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

yes

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

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

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

rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable 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.