DBMS > IBM Db2 Event Store vs. OrigoDB vs. Snowflake vs. Splunk

System Properties Comparison IBM Db2 Event Store vs. OrigoDB vs. Snowflake vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Event Store optimized for Internet of Things use cases

A fully ACID in-memory object graph database

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

Analytics Platform for Big Data

Primary database model

Event Store
Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Search engine

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

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.ibm.com/products/db2-event-store

origodb.com

www.snowflake.com

www.splunk.com

Technical documentation

www.ibm.com/docs/en/db2-event-store

origodb.com/docs

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

IBM

Robert Friberg et al

Snowflake Computing Inc.

Splunk Inc.

Initial release

2017

2009

under the name LiveDB

2014

2003

Current release

2.0

License

Commercial or Open Source

commercial

free developer edition available

Open Source

commercial

Limited free edition and free developer edition 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

C and C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.Net

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

Domain Events

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Source-replica replication

yes

Multi-source 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

Eventual Consistency

Foreign keys

Referential integrity

depending on model

yes

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

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

Write ahead log

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

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

Access rights for users and roles

More information provided by the system vendor

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.