DBMS > Microsoft Azure Cosmos DB vs. Splunk vs. TypeDB

System Properties Comparison Microsoft Azure Cosmos DB vs. Splunk vs. TypeDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

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
Graph DBMS
Key-value store
Wide column store

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.

Secondary database models

Spatial DBMS

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

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

Website

azure.microsoft.com/services/cosmos-db

www.splunk.com

typedb.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

docs.splunk.com/Documentation/Splunk

typedb.com/docs

Developer

Microsoft

Splunk Inc.

Vaticle

Initial release

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

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST

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

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java
JavaScript
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

by using Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication

by using Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

by using Apache Kafka and Apache Zookeeper

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

substituted by the relationship feature

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights can be defined down to the item level

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.