DBMS > Atos Standard Common Repository vs. GeoMesa vs. Machbase Neo vs. TimescaleDB

System Properties Comparison Atos Standard Common Repository vs. GeoMesa vs. Machbase Neo vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Atos Standard Common Repository  Xexclude from comparison	GeoMesa  Xexclude from comparison	Machbase Neo Former name was Infiniflux  Xexclude from comparison	TimescaleDB  Xexclude from comparison
	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	GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.	TimeSeries DBMS for AIoT and BigData	A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL
Primary database model	Document store Key-value store	Spatial DBMS	Time Series DBMS	Time Series DBMS
Secondary database models				Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart		Score 0.86 Rank #205   Overall #4   Spatial DBMS	Score 0.17 Rank #337   Overall #30   Time Series DBMS	Score 4.46 Rank #71   Overall #5   Time Series DBMS
Website	atos.net/en/convergence-creators/portfolio/standard-common-repository	www.geomesa.org	machbase.com	www.timescale.com
Technical documentation		www.geomesa.org/­documentation/­stable/­user/­index.html	machbase.com/­dbms	docs.timescale.com
Developer	Atos Convergence Creators	CCRi and others	Machbase	Timescale
Initial release	2016	2014	2013	2017
Current release	1703	5.0.0, May 2024	V8.0, August 2023	2.15.0, May 2024
License Commercial or Open Source	commercial	Open Source Apache License 2.0	commercial free test version available	Open Source Apache 2.0
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	Scala	C	C
Server operating systems	Linux		Linux macOS Windows	Linux OS X Windows
Data scheme	Schema and schema-less with LDAP views	yes	yes	yes
Typing predefined data types such as float or date	optional	yes	yes	numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types
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	no	yes
Secondary indexes	yes	yes	yes	yes
SQL Support of SQL	no	no	SQL-like query language	yes full PostgreSQL SQL syntax
APIs and other access methods	LDAP		gRPC HTTP REST JDBC MQTT (Message Queue Telemetry Transport) ODBC	ADO.NET JDBC native C library ODBC streaming API for large objects
Supported programming languages	All languages with LDAP bindings		C C# C++ Go Java JavaScript PHP via ODBC Python R via ODBC Scala	.Net C C++ Delphi Java JDBC JavaScript Perl PHP Python R Ruby Scheme Tcl
Server-side scripts Stored procedures	no	no	no	user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell
Triggers	yes	no	no	yes
Partitioning methods Methods for storing different data on different nodes	Sharding cell division	depending on storage layer	Sharding	yes, across time and space (hash partitioning) attributes
Replication methods Methods for redundantly storing data on multiple nodes	yes	depending on storage layer	selectable replication factor	Source-replica replication with hot standby and reads on replicas
MapReduce Offers an API for user-defined Map/Reduce methods		yes	no	no
Consistency concepts Methods to ensure consistency in a distributed system	Immediate Consistency or Eventual Consistency depending on configuration	depending on storage layer		Immediate Consistency
Foreign keys Referential integrity	no	no	no	yes
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	yes
Durability Support for making data persistent	yes	yes	no	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes	depending on storage layer	yes volatile and lookup table	no
User concepts Access control	LDAP bind authentication	yes depending on the DBMS used for storage	simple password-based access control	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
	Atos Standard Common Repository	GeoMesa	Machbase Neo Former name was Infiniflux	TimescaleDB
DB-Engines blog posts		Spatial database management systems 6 April 2021, Matthias Gelbmann show all
Recent citations in the news				TimescaleDB Is a Vector Database Now, Too 25 September 2023, Datanami Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers 4 April 2024, PR Newswire Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL 18 March 2019, Microsoft Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data 22 February 2022, Business Wire Timescale announces $15M investment and new enterprise version of TimescaleDB 29 January 2019, TechCrunch provided by Google News

Share this page