DBMS > Atos Standard Common Repository vs. FileMaker vs. Microsoft Azure Cosmos DB vs. RDF4J

System Properties Comparison Atos Standard Common Repository vs. FileMaker vs. Microsoft Azure Cosmos DB vs. RDF4J

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

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

Globally distributed, horizontally scalable, multi-model database service

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

RDF store

Secondary database models

Spatial DBMS

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

Score	45.20
Rank	#20	Overall
	#14	Relational DBMS

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Website

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

www.claris.com/filemaker

azure.microsoft.com/services/cosmos-db

rdf4j.org

Technical documentation

www.claris.com/resources/documentation

learn.microsoft.com/azure/cosmos-db

rdf4j.org/documentation

Developer

Atos Convergence Creators

Claris

a subsidiary of Apple

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2016

1983

2014

2004

Current release

1703

19.4.1, November 2021

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Server operating systems

Linux

iOS

client part only
Linux
OS X
Windows

hosted

Linux
OS X
Unix
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

optional

yes

JSON types

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

A http query request can return the data in XML format

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language

APIs and other access methods

LDAP

Filemaker WebDirect
JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages with LDAP bindings

PHP

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Java
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication, warm standby

since Version 14

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

simple rights management via user accounts and connection to external directory services

Access rights can be defined down to the item level

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.