DBMS > Amazon Redshift vs. BigObject vs. GeoMesa vs. Interbase vs. Realm

System Properties Comparison Amazon Redshift vs. BigObject vs. GeoMesa vs. Interbase vs. Realm

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Light-weight proven RDBMS

originally from Borland

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Spatial DBMS

Relational DBMS

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

aws.amazon.com/redshift

bigobject.io

www.geomesa.org

www.embarcadero.com/products/interbase

realm.io

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

www.geomesa.org/documentation/stable/user/index.html

docs.embarcadero.com/products/interbase

realm.io/docs

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

CCRi and others

Embarcadero

Realm, acquired by MongoDB in May 2019

Initial release

2012

2015

2014

1984

2014

Current release

5.0.0, May 2024

InterBase 2020, December 2019

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache License 2.0

commercial

Open Source

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

Scala

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Android
iOS
Linux
OS X
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

yes

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.

export as XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

Interbase procedure and trigger language

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

depending on storage layer

Interbase Change Views

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Multiversion concurreny control

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

depending on storage layer

yes

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes

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.