DBMS > FatDB vs. InfluxDB vs. Snowflake vs. Spark SQL vs. YottaDB

System Properties Comparison FatDB vs. InfluxDB vs. Snowflake vs. Spark SQL vs. YottaDB

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

Cloud-based data warehousing service for structured and semi-structured data

Spark SQL is a component on top of 'Spark Core' for structured data processing

A fast and solid embedded Key-value store

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

with GEO package

Relational DBMS

using the Octo plugin

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

Score	25.83
Rank	#28	Overall
	#1	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

www.influxdata.com/products/influxdb-overview

www.snowflake.com

spark.apache.org/sql

yottadb.com

Technical documentation

docs.influxdata.com/influxdb

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

yottadb.com/resources/documentation

Developer

FatCloud

Snowflake Computing Inc.

Apache Software Foundation

YottaDB, LLC

Initial release

2012

2013

2014

2001

Current release

2.7.6, April 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

MIT-License; commercial enterprise version available

commercial

Open Source

Apache 2.0

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Server operating systems

Windows

Linux
OS X

through Homebrew

hosted

Linux
OS X
Windows

Docker
Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data and Strings

yes

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

yes

SQL-like DML and DDL statements

by using the Octo plugin

APIs and other access methods

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

HTTP API
JSON over UDP

CLI Client
JDBC
ODBC

JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

JavaScript (Node.js)
Python

Java
Python
R
Scala

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Triggers

yes

via applications

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

in enterprise version only

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

in enterprise version only

yes

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and groups based on OS-security mechanisms

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

What is DevRel at InfluxData
21 May 2024

An Introductory Guide to Grafana Alerts
16 May 2024

What to Expect When You’re Expecting InfluxDB: A Guide
14 May 2024

Introduction to Apache Iceberg
9 May 2024

Converting Timestamp to Date in Java
7 May 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.