DBMS > FatDB vs. InfluxDB vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison FatDB vs. InfluxDB vs. Oracle Berkeley DB vs. RocksDB

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 in-process key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Spatial DBMS

with GEO package

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

Score	26.56
Rank	#28	Overall
	#1	Time Series DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

www.influxdata.com/products/influxdb-overview

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

Technical documentation

docs.influxdata.com/influxdb

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

FatCloud

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2012

2013

1994

2013

Current release

2.7.5, January 2024

18.1.40, May 2020

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

MIT-License; commercial enterprise version available

Open Source

commercial license available

Open Source

BSD

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

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Windows

Linux
OS X

through Homebrew

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

Numeric data and Strings

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

HTTP API
JSON over UDP

C++ API
Java API

Supported programming languages

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

.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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

in enterprise version only

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

in enterprise version only

Source-replica replication

yes

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

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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

Depending on used storage engine

yes

User concepts

Access control

Can implement custom security layer via applications

simple rights management via user accounts

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

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

Infrastructure Monitoring Basics: Getting Started with Telegraf, InfluxDB, and Grafana
5 April 2024

Comparing Dates in Java: A Tutorial
3 April 2024

Python ARIMA Tutorial
29 March 2024

Time Series, InfluxDB, and Vector Databases
26 March 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.