DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. GridDB vs. Interbase vs. Vertica

System Properties Comparison Amazon DynamoDB vs. Atos Standard Common Repository vs. GridDB vs. Interbase vs. Vertica

Editorial information provided by DB-Engines

Name

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

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Scalable in-memory time series database optimized for IoT and Big Data

Light-weight proven RDBMS

originally from Borland

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Column oriented

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	10.06
Rank	#42	Overall
	#26	Relational DBMS

Website

aws.amazon.com/dynamodb

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

griddb.net

www.embarcadero.com/products/interbase

www.vertica.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.griddb.net

docs.embarcadero.com/products/interbase

vertica.com/documentation

Developer

Amazon

Atos Convergence Creators

Toshiba Corporation

Embarcadero

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2012

2016

2013

1984

2005

Current release

1703

5.1, August 2022

InterBase 2020, December 2019

12.0.3, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

hosted

Linux

Android
iOS
Linux
OS X
Windows

Linux

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes

optional

yes

numerical, string, blob, geometry, boolean, timestamp

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

export as XML data possible

Secondary indexes

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

RESTful HTTP API

LDAP

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

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

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

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

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

by integration with AWS Lambda

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Interbase Change Views

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

Atomic execution of specific operations

ACID at container level

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

Cost-based models and subscription-based models are both available. One license is...
» 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.