DBMS > Apache Impala vs. Ehcache vs. Microsoft SQL Server vs. Riak TS

System Properties Comparison Apache Impala vs. Ehcache vs. Microsoft SQL Server vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A widely adopted Java cache with tiered storage options

Microsofts flagship relational DBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

impala.apache.org

www.ehcache.org

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

Technical documentation

impala.apache.org/impala-docs.html

www.ehcache.org/documentation

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

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Terracotta Inc, owned by Software AG

Microsoft

Open Source, formerly Basho Technologies

Initial release

2013

2009

1989

2015

Current release

4.1.0, June 2022

3.10.0, March 2022

SQL Server 2022, November 2022

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

Open Source

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Java

C++

Erlang

Server operating systems

Linux

All OS with a Java VM

Linux
Windows

Linux
OS X

Data scheme

yes

schema-free

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

restricted

SQL

Support of SQL

SQL-like DML and DDL statements

yes

yes, limited

APIs and other access methods

JDBC
ODBC

JCache

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

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

Java

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

Erlang

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

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

yes

by using Terracotta Server

yes, but depending on the SQL-Server Edition

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

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.