DBMS > Atos Standard Common Repository vs. Firebird vs. Geode vs. ToroDB

System Properties Comparison Atos Standard Common Repository vs. Firebird vs. Geode vs. ToroDB

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.

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

Firebird is an open source RDBMS forked from Borland's InterBase

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Document store

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

Score	21.06
Rank	#31	Overall
	#19	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Website

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

www.firebirdsql.org

geode.apache.org

github.com/torodb/server

Technical documentation

www.firebirdsql.org/en/reference-manuals

geode.apache.org/docs

Developer

Atos Convergence Creators

Firebird Foundation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

8Kdata

Initial release

2016

2000

As fork of Borland's InterBase

2002

2016

Current release

1703

5.0.0, January 2024

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

Open Source

Apache Version 2; commercial licenses available as Gemfire

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.

Implementation language

Java

C and C++

Java

Server operating systems

Linux

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java 7 VM

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

APIs and other access methods

LDAP

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

PSQL

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

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

Eventual 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

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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

Users with fine-grained authorization concept

Access rights per client and object definable

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.

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

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

provided by Google News

DoNot Team's New Firebird Backdoor Hits Pakistan and Afghanistan
23 October 2023, The Hacker News

FIREBIRD'S HUBBARD TALKS DATA, AI, TIKTOK
14 December 2023, HITS Daily Double

US and Australian police arrested Firebird RAT author and operator
15 April 2024, securityaffairs.com

Albany Firebirds single-game tickets on sale Friday
29 February 2024, Troy Record

Lines of the Firebird: Inside The Photography & Poetry Project Exploring The Renaissance of Female Power
6 September 2023, Country and Town House

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page