DBMS > dBASE vs. Firebase Realtime Database vs. Snowflake

System Properties Comparison dBASE vs. Firebase Realtime Database vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.dbase.com

firebase.google.com/products/realtime-database

www.snowflake.com

Technical documentation

www.dbase.com/support/knowledgebase

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Google

acquired by Google 2014

Snowflake Computing Inc.

Initial release

1979

2012

2014

Current release

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.

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

limited functionality with using 'rules'

user defined functions

Triggers

Callbacks are triggered when data changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

yes

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.

User concepts

Access control

Access rights for users and roles

yes, based on authentication and database rules

Users with fine-grained authorization concept, user roles and pluggable authentication

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.