DBMS > Atos Standard Common Repository vs. FatDB vs. Infobright vs. MonetDB

System Properties Comparison Atos Standard Common Repository vs. FatDB vs. Infobright vs. MonetDB

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A relational database management system that stores data in columns

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Website

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

ignitetech.com/softwarelibrary/infobrightdb

www.monetdb.org

Technical documentation

www.monetdb.org/Documentation

Developer

Atos Convergence Creators

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

MonetDB BV

Initial release

2016

2012

2005

2004

Current release

1703

Dec2023 (11.49), December 2023

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Mozilla Public License 2.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

Server operating systems

Linux

Windows

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL 2003 with some extensions

APIs and other access methods

LDAP

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

via applications

yes, in SQL, C, R

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Sharding via remote tables

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

none

Source-replica replication available in experimental status

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate 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

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

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

Recent citations in the news

In 2024 the MonetDB Foundation was established for the preservation, maintenance and further development of the ...
31 January 2024, Centrum Wiskunde & Informatica (CWI)

MonetDB Secures Investment From (and Partners With) ServiceNow
9 December 2021, Datanami

PostgreSQL, MonetDB, and Too-Big-for-Memory Data in R - Part I - DataScienceCentral.com
6 April 2018, Data Science Central

How MonetDB Exploits Modern CPU Performance | by Dwi Prasetyo Adi Nugroho
14 January 2020, Towards Data Science

MonetDB Solutions secures investment from ServiceNow
30 September 2019, Centrum Wiskunde & Informatica (CWI)

provided by Google News

Share this page