DBMS > Apache Impala vs. Drizzle vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Splunk

System Properties Comparison Apache Impala vs. Drizzle vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Splunk

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Analytic DBMS for Hadoop

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Document store
Graph DBMS
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

impala.apache.org

cloud.google.com/datastore

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

www.splunk.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/datastore/docs

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

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Drizzle project, originally started by Brian Aker

Google

Microsoft

Splunk Inc.

Initial release

2013

2008

1989

2003

Current release

4.1.0, June 2022

7.2.4, September 2012

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

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

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

Linux
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

SQL-like query language (GQL)

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC

JDBC

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

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

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

.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

user defined functions and integration of map-reduce

using Google App Engine

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

yes

Triggers

hooks for callbacks inside the server can be used.

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

selectable replication factor

Multi-source replication
Source-replica replication

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

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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.

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.