DBMS > dBASE vs. GeoSpock vs. Google Cloud Bigtable vs. GridDB vs. RocksDB

System Properties Comparison dBASE vs. GeoSpock vs. Google Cloud Bigtable vs. GridDB vs. RocksDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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.

Spatial and temporal data processing engine for extreme data scale

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store
Wide column store

Time Series DBMS

Key-value store

Secondary database models

Time Series DBMS

Key-value 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	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.dbase.com

geospock.com

cloud.google.com/bigtable

griddb.net

rocksdb.org

Technical documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigtable/docs

docs.griddb.net

github.com/facebook/rocksdb/wiki

Developer

Asthon Tate

GeoSpock

Google

Toshiba Corporation

Facebook, Inc.

Initial release

1979

2015

2013

Current release

dBASE 2019, 2019

2.0, September 2019

5.1, August 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

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

Open Source

BSD

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, Javascript

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

JDBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

dBase proprietary IDE

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

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Internal replication in Colossus, and regional replication between two clusters in different zones

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate consistency within container, eventual consistency across containers

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

Atomic single-row operations

ACID at container level

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

Access rights for users and roles

Access rights for users can be defined per table

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

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

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

Competitive advantages

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

Typical application scenarios

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

Key customers

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

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.