DBMS > Elasticsearch vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Splunk

System Properties Comparison Elasticsearch vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Splunk

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Microsofts flagship relational DBMS

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

www.elastic.co/elasticsearch

cloud.google.com/datastore

www.microsoft.com/en-us/sql-server

www.splunk.com

Technical documentation

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

cloud.google.com/datastore/docs

learn.microsoft.com/en-US/sql/sql-server

docs.splunk.com/Documentation/Splunk

Developer

Elastic

Google

Microsoft

Splunk Inc.

Initial release

2010

2008

1989

2003

Current release

8.6, January 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Elastic License

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

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

C++

Server operating systems

All OS with a Java VM

hosted

Linux
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

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

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

Splunk Search Processing Language for search commands

APIs and other access methods

Java API
RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

using Google App Engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

by using the 'percolation' feature

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

using Google Cloud Dataflow

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 or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.