DBMS > FatDB vs. Machbase Neo vs. Newts vs. Prometheus vs. TimescaleDB

System Properties Comparison FatDB vs. Machbase Neo vs. Newts vs. Prometheus vs. TimescaleDB

Editorial information provided by DB-Engines

Name

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

Description

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

TimeSeries DBMS for AIoT and BigData

Time Series DBMS based on Cassandra

Open-source Time Series DBMS and monitoring system

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store
Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

machbase.com

opennms.github.io/newts

prometheus.io

www.timescale.com

Technical documentation

machbase.com/dbms

github.com/OpenNMS/newts/wiki

prometheus.io/docs

docs.timescale.com

Developer

FatCloud

Machbase

OpenNMS Group

Timescale

Initial release

2012

2013

2014

2015

2017

Current release

V8.0, August 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

free test version available

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache 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

Windows

Linux
macOS
Windows

Linux
OS X
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

HTTP REST
Java API

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

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

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

by Federation

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

volatile and lookup table

User concepts

Access control

Can implement custom security layer via applications

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

Recent citations in the news

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus | Amazon Web Services
10 March 2024, AWS Blog

Exadata Real-Time Insight - Quick Start
3 April 2024, blogs.oracle.com

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

OpenTelemetry vs. Prometheus: You can’t fix what you can’t see
29 March 2024, IBM

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

provided by Google 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, businesswire.com

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Share this page