DBMS > BoltDB vs. PostGIS vs. Sequoiadb vs. Splunk vs. TimescaleDB

System Properties Comparison BoltDB vs. PostGIS vs. Sequoiadb vs. Splunk vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Spatial extension of PostgreSQL

NewSQL database with distributed OLTP and SQL

Analytics Platform for Big Data

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Key-value store

Spatial DBMS

Document store
Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

github.com/boltdb/bolt

Technical documentation

postgis.net/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.splunk.com/Documentation/Splunk

docs.timescale.com

Developer

Sequoiadb Ltd.

Splunk Inc.

Timescale

Initial release

2013

2005

2013

2003

2017

Current release

3.4.2, February 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL v2.0

Open Source

Server: AGPL; Client: Apache V2

commercial

Limited free edition and free developer edition available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL-like query language

Splunk Search Processing Language for search commands

yes

full PostgreSQL SQL syntax

APIs and other access methods

proprietary protocol using JSON

HTTP REST

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
C++
Java
PHP
Python

C#
Java
JavaScript
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

Source-replica replication

Multi-source replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Document is locked during a transaction

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

yes

based on PostgreSQL

simple password-based access control

Access rights for users and roles

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

Three Reasons DevOps Should Consider Rocky Linux 9.4
15 May 2024, DevOps.com

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, azure.microsoft.com

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

Timescale announces $15M investment and new enterprise version of TimescaleDB
29 January 2019, TechCrunch

provided by Google News

Share this page