DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. dBASE vs. Google Cloud Firestore

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. dBASE vs. Google Cloud Firestore

Please select another system to include it in the comparison.

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

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Website

aws.amazon.com/redshift

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

www.dbase.com

firebase.google.com/products/firestore

Technical documentation

docs.aws.amazon.com/redshift

www.dbase.com/support/knowledgebase

firebase.google.com/docs/firestore

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Asthon Tate

Google

Initial release

2012

2016

1979

2017

Current release

1703

dBASE 2019, 2019

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

Java

Server operating systems

hosted

Linux

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

yes

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

LDAP

none

The IDE can access other DBMS or ODBC-sources.

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

dBase proprietary IDE

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Server-side scripts

Stored procedures

user defined functions

in Python

The IDE can access stored procedures in other database systems.

yes, Firebase Rules & Cloud Functions

Triggers

yes

yes, with Cloud Functions

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

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

Access rights for users and roles

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.