DBMS > Elasticsearch vs. Google BigQuery vs. Splunk vs. SurrealDB

System Properties Comparison Elasticsearch vs. Google BigQuery vs. Splunk vs. SurrealDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

Analytics Platform for Big Data

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Search engine

Relational DBMS

Search engine

Document store
Graph DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.86
Rank	#203	Overall
	#34	Document stores
	#18	Graph DBMS

Website

www.elastic.co/elasticsearch

cloud.google.com/bigquery

www.splunk.com

surrealdb.com

Technical documentation

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

cloud.google.com/bigquery/docs

docs.splunk.com/Documentation/Splunk

surrealdb.com/docs

Developer

Elastic

Google

Splunk Inc.

SurrealDB Ltd

Initial release

2010

2003

2022

Current release

8.6, January 2023

v1.5.0, May 2024

License

Commercial or Open Source

Open Source

Elastic License

commercial

Limited free edition and free developer edition available

Open Source

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

Java

Rust

Server operating systems

All OS with a Java VM

hosted

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

schema-free

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

yes

schema-free

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

Splunk Search Processing Language for search commands

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

HTTP REST

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

Transaction concepts

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

Since BigQuery is designed for querying data

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.

Memcached and Redis integration

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

yes, based on authentication and database rules

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.