DBMS > Atos Standard Common Repository vs. Axibase vs. FatDB vs. Oracle Berkeley DB

System Properties Comparison Atos Standard Common Repository vs. Axibase vs. FatDB vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Atos Standard Common Repository  Xexclude from comparison	Axibase  Xexclude from comparison	FatDB  Xexclude from comparison	Oracle Berkeley DB  Xexclude from comparison
	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	Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization	A .NET NoSQL DBMS that can integrate with and extend SQL Server.	Widely used in-process key-value store
Primary database model	Document store Key-value store	Time Series DBMS	Document store Key-value store	Key-value store supports sorted and unsorted key sets Native XML DBMS in the Oracle Berkeley DB XML version
DB-Engines Ranking measures the popularity of database management systems Trend Chart		Score 0.35 Rank #282   Overall #25   Time Series DBMS		Score 2.01 Rank #126   Overall #21   Key-value stores #3   Native XML DBMS
Website	atos.net/en/convergence-creators/portfolio/standard-common-repository	axibase.com/­docs/­atsd/­finance		www.oracle.com/­database/­technologies/­related/­berkeleydb.html
Technical documentation				docs.oracle.com/­cd/­E17076_05/­html/­index.html
Developer	Atos Convergence Creators	Axibase Corporation	FatCloud	Oracle originally developed by Sleepycat, which was acquired by Oracle
Initial release	2016	2013	2012	1994
Current release	1703	15585		18.1.40, May 2020
License Commercial or Open Source	commercial	commercial Community Edition (single node) is free, Enterprise Edition (distributed) is paid	commercial	Open Source commercial license available
Cloud-based only Only available as a cloud service	no	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Java	Java	C#	C, Java, C++ (depending on the Berkeley DB edition)
Server operating systems	Linux	Linux	Windows	AIX Android FreeBSD iOS Linux OS X Solaris VxWorks Windows
Data scheme	Schema and schema-less with LDAP views	yes	schema-free	schema-free
Typing predefined data types such as float or date	optional	yes short, integer, long, float, double, decimal, string	yes	no
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	no		yes only with the Berkeley DB XML edition
Secondary indexes	yes	no	yes	yes
SQL Support of SQL	no	SQL-like query language	no Via inetgration in SQL Server	yes SQL interfaced based on SQLite is available
APIs and other access methods	LDAP	JDBC Proprietary protocol (Network API) RESTful HTTP API	.NET Client API LINQ RESTful HTTP API RPC Windows WCF Bindings
Supported programming languages	All languages with LDAP bindings	Go Java PHP Python R Ruby	C#	.Net Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET others Third-party libraries to manipulate Berkeley DB files are available for many languages C C# C++ Java JavaScript (Node.js) 3rd party binding Perl Python Tcl
Server-side scripts Stored procedures	no	yes	yes via applications	no
Triggers	yes	yes	yes via applications	yes only for the SQL API
Partitioning methods Methods for storing different data on different nodes	Sharding cell division	Sharding	Sharding	none
Replication methods Methods for redundantly storing data on multiple nodes	yes	Source-replica replication	selectable replication factor	Source-replica replication
MapReduce Offers an API for user-defined Map/Reduce methods		yes	yes	no
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	no	no	no	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	Atomic execution of specific operations	no	no	ACID
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes			yes
User concepts Access control	LDAP bind authentication		no Can implement custom security layer via applications	no
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
	Atos Standard Common Repository	Axibase	FatDB	Oracle Berkeley DB
Recent citations in the news	Infographic: What makes a Mobile Operator's setup future proof? 10 February 2024, Atos provided by Google News	The Ultimate ATV Test: Suzuki's King Quad 750 AXI Rugged Package vs. Alaska's Hunting Season 20 April 2021, Outdoor Life provided by Google News		ACM recognizes far-reaching technical achievements with special awards 26 May 2021, EurekAlert What You Need to Know About NoSQL Databases 17 February 2012, Forbes Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag 5 March 2019, ADT Magazine Margo I. Seltzer | Berkman Klein Center 18 August 2020, Berkman Klein Center How to store financial market data for backtesting 26 January 2019, Towards Data Science provided by Google News

Share this page