DBMS > FatDB vs. Snowflake vs. Splunk vs. TypeDB

System Properties Comparison FatDB vs. Snowflake vs. Splunk vs. TypeDB

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.

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

Analytics Platform for Big Data

TypeDB is a strongly-typed database with a rich and logical type system and TypeQL as its query language

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Graph DBMS
Relational DBMS

Often described as a 'hyper-relational' database, since it implements the 'Entity-Relationship Paradigm' to manage complex data structures and ontologies.

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.65
Rank	#234	Overall
	#20	Graph DBMS
	#107	Relational DBMS

Website

www.snowflake.com

www.splunk.com

typedb.com

Technical documentation

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

typedb.com/docs

Developer

FatCloud

Snowflake Computing Inc.

Splunk Inc.

Vaticle

Initial release

2012

2014

2003

2016

Current release

2.26.3, January 2024

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

Open Source

GPL Version 3, commercial licenses available

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

Java

Server operating systems

Windows

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

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

yes

Splunk Search Processing Language for search commands

APIs and other access methods

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

CLI Client
JDBC
ODBC

HTTP REST

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (Visualisation software- previously TypeDB Workbase)

Supported programming languages

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

All JVM based languages
Groovy
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

yes

via applications

user defined functions

yes

Triggers

yes

via applications

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

by using Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication

by using Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

by using Apache Kafka and Apache Zookeeper

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

substituted by the relationship feature

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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.

User concepts

Access control

Can implement custom security layer via applications

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

Access rights for users and roles

yes

at REST API level; other APIs in progress

More information provided by the system vendor

Specific characteristics

TypeDB is a polymorphic database with a conceptual data model, a strong subtyping...
» more

Competitive advantages

TypeDB provides a new level of expressivity, extensibility, interoperability, and...
» more

Typical application scenarios

Life sciences : TypeDB makes working with biological data much easier and accelerates...
» more

Licensing and pricing models

Apache f or language drivers, and AGPL and Commercial for the database server. The...
» more

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.