DBMS > Google Cloud Datastore vs. OpenEdge vs. Oracle vs. Teradata Aster

System Properties Comparison Google Cloud Datastore vs. OpenEdge vs. Oracle vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Application development environment with integrated database management system

Widely used RDBMS

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

cloud.google.com/datastore

www.progress.com/openedge

www.oracle.com/database

Technical documentation

cloud.google.com/datastore/docs

documentation.progress.com/output/ua/OpenEdge_latest

docs.oracle.com/en/database

Developer

Google

Progress Software Corporation

Oracle

Teradata

Initial release

2008

1984

1980

2005

Current release

OpenEdge 12.2, March 2020

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

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 C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes, details here

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

close to SQL 92

yes

with proprietary extensions

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

using Google App Engine

yes

PL/SQL

also stored procedures in Java possible

R packages

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

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

Users and groups

fine grained access rights according to SQL-standard

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.