DBMS > FatDB vs. InfluxDB vs. MySQL vs. OrigoDB

System Properties Comparison FatDB vs. InfluxDB vs. MySQL vs. OrigoDB

Please select another system to include it in the comparison.

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.

DBMS for storing time series, events and metrics

Widely used open source RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Secondary database models

Spatial DBMS

with GEO package

Document store
Spatial DBMS

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

Score	25.83
Rank	#28	Overall
	#1	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

www.influxdata.com/products/influxdb-overview

www.mysql.com

origodb.com

Technical documentation

docs.influxdata.com/influxdb

dev.mysql.com/doc

origodb.com/docs

Developer

FatCloud

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Initial release

2012

2013

1995

2009

under the name LiveDB

Current release

2.7.6, April 2024

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

MIT-License; commercial enterprise version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

Windows

Linux
OS X

through Homebrew

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data and Strings

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

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

HTTP API
JSON over UDP

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Perl
PHP
Python
R
Ruby
Rust
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax

yes

Triggers

yes

via applications

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

in enterprise version only

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

in enterprise version only

Multi-source replication
Source-replica replication

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Depending on used storage engine

yes

User concepts

Access control

Can implement custom security layer via applications

simple rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

More information provided by the system vendor

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

News

Converting Timestamp to Date in Java
7 May 2024

A Detailed Guide to C# TimeSpan
2 May 2024

The Final Frontier: Using InfluxDB on the International Space Station
30 April 2024

Getting the Current Time in C#: A Guide
26 April 2024

Sync Data from InfluxDB v2 to v3 With the Quix Template
8 April 2024

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.