DBMS > Amazon DynamoDB vs. Apache Drill vs. Splunk vs. Tibero

System Properties Comparison Amazon DynamoDB vs. Apache Drill vs. Splunk vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Analytics Platform for Big Data

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store
Key-value store

Document store
Relational DBMS

Search engine

Relational DBMS

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	1.46
Rank	#151	Overall
	#70	Relational DBMS

Website

aws.amazon.com/dynamodb

drill.apache.org

www.splunk.com

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/dynamodb

drill.apache.org/docs

docs.splunk.com/Documentation/Splunk

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon

Apache Software Foundation

Splunk Inc.

TmaxSoft

Initial release

2012

2003

Current release

1.20.3, January 2023

7, September 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

Limited free edition and free developer edition available

commercial

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 Assembler

Server operating systems

hosted

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

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

SQL SELECT statement is SQL:2003 compliant

Splunk Search Processing Language for search commands

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

HTTP REST

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C++

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

Persistent Stored Procedure (PSM)

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

planned for next version

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Depending on the underlying data source

Access rights for users and roles

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.