DBMS > BoltDB vs. Elasticsearch vs. Postgres-XL vs. Splunk

System Properties Comparison BoltDB vs. Elasticsearch vs. Postgres-XL vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

github.com/boltdb/bolt

www.elastic.co/elasticsearch

www.postgres-xl.org

www.splunk.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.postgres-xl.org/documentation

docs.splunk.com/Documentation/Splunk

Developer

Elastic

Splunk Inc.

Initial release

2013

2010

2014

since 2012, originally named StormDB

2003

Current release

8.6, January 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

MIT License

Open Source

Elastic License

Open Source

Mozilla public license

commercial

Limited free edition and free developer edition available

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
macOS

Linux
OS X
Solaris
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

Splunk Search Processing Language for search commands

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

HTTP REST

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

MVCC

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

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.

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

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.

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

PostgreSQL is the DBMS of the Year 2017
2 January 2018, Paul Andlinger, Matthias Gelbmann

Elasticsearch moved into the top 10 most popular database management systems
3 July 2017, Matthias Gelbmann

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

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

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

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.com

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

provided by Google News

Introducing Elasticsearch Vector Database to Azure OpenAI Service On Your Data (Preview)
26 March 2024, GovTech

Elasticsearch Open Inference API Supports Cohere Rerank 3
11 April 2024, Business Wire

ElasticSearch Goes Deep on OpenTelemetry with eBPF Donation
13 March 2024, The New Stack

12K Misconfigured Elasticsearch Buckets Ravaged by Extortionists
29 November 2023, Dark Reading

AWS Marketplace: Elastic Cloud (Elasticsearch Service) Comments
18 March 2024, AWS Blog

provided by Google News

Share this page