DBMS > Cubrid vs. dBASE vs. Google Cloud Spanner vs. Snowflake

System Properties Comparison Cubrid vs. dBASE vs. Google Cloud Spanner vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

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

Primary database model

Relational DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cubrid.com (korean)
cubrid.org (english)

www.dbase.com

cloud.google.com/spanner

www.snowflake.com

Technical documentation

cubrid.org/manuals

www.dbase.com/support/knowledgebase

cloud.google.com/spanner/docs

docs.snowflake.net/manuals/index.html

Developer

CUBRID Corporation, CUBRID Foundation

Asthon Tate

Google

Snowflake Computing Inc.

Initial release

2008

1979

2017

2014

Current release

11.0, January 2021

dBASE 2019, 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Server operating systems

Linux
Windows

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

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

Query statements complying to ANSI 2011

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

none

The IDE can access other DBMS or ODBC-sources.

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

dBase proprietary IDE

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

The IDE can access stored procedures in other database systems.

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication with 3 replicas for regional instances.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

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

ACID

Strict serializable isolation

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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

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.