DBMS > Atos Standard Common Repository vs. ClickHouse vs. Faircom DB vs. FileMaker vs. ToroDB

System Properties Comparison Atos Standard Common Repository vs. ClickHouse vs. Faircom DB vs. FileMaker vs. ToroDB

Editorial information provided by DB-Engines

Name

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

ToroDB 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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store

Secondary database models

Time Series DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Website

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

clickhouse.com

www.faircom.com/products/faircom-db

www.claris.com/filemaker

github.com/torodb/server

Technical documentation

clickhouse.com/docs

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.claris.com/resources/documentation

Developer

Atos Convergence Creators

Clickhouse Inc.

FairCom Corporation

Claris

a subsidiary of Apple

8Kdata

Initial release

2016

1979

1983

2016

Current release

1703

v24.4.1.2088-stable, May 2024

V12, November 2020

19.4.1, November 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Restricted, free version available

commercial

Open Source

AGPL-V3

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

Java

C++

ANSI C, C++

Java

Server operating systems

Linux

FreeBSD
Linux
macOS

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

iOS

client part only
Linux
OS X
Windows

All OS with a Java 7 VM

Data scheme

Schema and schema-less with LDAP views

yes

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes, ANSI SQL with proprietary extensions

yes

via plugins

APIs and other access methods

LDAP

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Filemaker WebDirect
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

PHP

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

key based and custom

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication, warm standby

since Version 14

Source-replica replication

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
Tunable consistency per server, database, table, and transaction

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

tunable from ACID to Eventually Consistent

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Fine grained access rights according to SQL-standard with additional protections for files

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

Access rights for users and roles

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.