DBMS > Atos Standard Common Repository vs. JaguarDB vs. PostGIS

System Properties Comparison Atos Standard Common Repository vs. JaguarDB vs. PostGIS

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

Performant, highly scalable DBMS for AI and IoT applications

Spatial extension of PostgreSQL

Primary database model

Document store
Key-value store

Key-value store
Vector DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

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

www.jaguardb.com

postgis.net

Technical documentation

www.jaguardb.com/support.html

postgis.net/documentation

Developer

Atos Convergence Creators

DataJaguar, Inc.

Initial release

2016

2015

2005

Current release

1703

3.3 July 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

GPL v2.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++

the server part. Clients available in other languages

Server operating systems

Linux

Data scheme

Schema and schema-less with LDAP views

yes

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

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

LDAP

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

based on PostgreSQL

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

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

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

rights management via user accounts

yes

based on PostgreSQL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Share this page