DBMS > Amazon Redshift vs. Google Cloud Bigtable vs. Interbase vs. Tibero

System Properties Comparison Amazon Redshift vs. Google Cloud Bigtable vs. Interbase vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Light-weight proven RDBMS

originally from Borland

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

aws.amazon.com/redshift

cloud.google.com/bigtable

www.embarcadero.com/products/interbase

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/bigtable/docs

docs.embarcadero.com/products/interbase

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon (based on PostgreSQL)

Google

Embarcadero

TmaxSoft

Initial release

2012

2015

1984

2003

Current release

InterBase 2020, December 2019

6, April 2015

License

Commercial or Open Source

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 and Assembler

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

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

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Go
Java
JavaScript (Node.js)
Python

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Interbase procedure and trigger language

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

Interbase Change Views

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

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 single-row 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

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.