DBMS > Apache Impala vs. Drizzle vs. Ignite vs. Microsoft SQL Server vs. Oracle Berkeley DB

System Properties Comparison Apache Impala vs. Drizzle vs. Ignite vs. Microsoft SQL Server vs. Oracle Berkeley DB

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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Microsofts flagship relational DBMS

Widely used in-process key-value store

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

impala.apache.org

ignite.apache.org

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

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

impala.apache.org/impala-docs.html

apacheignite.readme.io/docs

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

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Drizzle project, originally started by Brian Aker

Apache Software Foundation

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2013

2008

2015

1989

1994

Current release

4.1.0, June 2022

7.2.4, September 2012

Apache Ignite 2.6

SQL Server 2022, November 2022

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

commercial license 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

C++

C++, Java, .Net

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

ANSI-99 for query and DML statements, subset of DDL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

JDBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes (compute grid and cache interceptors can be used instead)

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

Triggers

hooks for callbacks inside the server can be used.

yes (cache interceptors and events)

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

yes (replicated cache)

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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.

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

Security Hooks for custom implementations

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.