DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. Databricks vs. Interbase vs. SiriDB

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. Databricks vs. Interbase vs. SiriDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Light-weight proven RDBMS

originally from Borland

Open Source Time Series DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.databricks.com

www.embarcadero.com/products/interbase

siridb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.databricks.com

docs.embarcadero.com/products/interbase

docs.siridb.com

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Databricks

Embarcadero

Cesbit

Initial release

2012

2016

2013

1984

2017

Current release

1703

InterBase 2020, December 2019

License

Commercial or Open Source

commercial

Open Source

MIT License

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

Server operating systems

hosted

Linux

hosted

Android
iOS
Linux
OS X
Windows

Linux

Data scheme

yes

Schema and schema-less with LDAP views

Flexible Schema (defined schema, partial schema, schema free)

yes

Typing

predefined data types such as float or date

yes

optional

yes

Numeric data

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC

LDAP

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Python
R
Scala

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

yes

Interbase procedure and trigger language

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Interbase Change Views

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

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

LDAP bind authentication

fine grained access rights according to SQL-standard

simple rights management via user accounts

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.