DBMS > Amazon Aurora vs. Apache Impala vs. EJDB vs. Interbase vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon Aurora vs. Apache Impala vs. EJDB vs. Interbase vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Analytic DBMS for Hadoop

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Light-weight proven RDBMS

originally from Borland

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

aws.amazon.com/rds/aurora

impala.apache.org

github.com/Softmotions/ejdb

www.embarcadero.com/products/interbase

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

impala.apache.org/impala-docs.html

github.com/Softmotions/ejdb/blob/master/README.md

docs.embarcadero.com/products/interbase

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Softmotions

Embarcadero

Microsoft

Initial release

2015

2013

2012

1984

2014

Current release

4.1.0, June 2022

InterBase 2020, December 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPLv2

commercial

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

hosted

Linux

server-less

Android
iOS
Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

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

export as XML data possible

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

in-process shared library

ADO.NET
JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Interbase procedure and trigger language

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

none

Interbase Change Views

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Multiversion concurreny control

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.