DBMS > LevelDB vs. ObjectBox vs. Snowflake vs. Splunk vs. Transbase

System Properties Comparison LevelDB vs. ObjectBox vs. Snowflake vs. Splunk vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Extremely fast embedded database for small devices, IoT and Mobile

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

Analytics Platform for Big Data

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Time Series DBMS

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

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

github.com/google/leveldb

objectbox.io

www.snowflake.com

www.splunk.com

www.transaction.de/en/products/transbase.html

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

docs.objectbox.io

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

www.transaction.de/en/products/transbase/features.html

Developer

Google

ObjectBox Limited

Snowflake Computing Inc.

Splunk Inc.

Transaction Software GmbH

Initial release

2011

2017

2014

2003

1987

Current release

1.23, February 2021

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache License 2.0

commercial

Limited free edition and free developer edition available

commercial

free development license

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++

C and C++

Server operating systems

Illumos
Linux
OS X
Windows

Android
iOS
Linux
macOS
Windows

hosted

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
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

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

Proprietary native API

CLI Client
JDBC
ODBC

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

online/offline synchronization between client and server

yes

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

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

User concepts

Access control

yes

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

Access rights for users and roles

fine grained access rights according to SQL-standard

More information provided by the system vendor

News

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

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.