DBMS > BigObject vs. Blueflood vs. dBASE vs. GeoMesa vs. Snowflake

System Properties Comparison BigObject vs. Blueflood vs. dBASE vs. GeoMesa vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Scalable TimeSeries DBMS based on Cassandra

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.bigobject.io

github.com/rax-maas/blueflood/wiki

www.dbase.com/support/knowledgebase

www.geomesa.org/documentation/stable/user/index.html

docs.snowflake.net/manuals/index.html

Developer

BigObject, Inc.

Rackspace

Asthon Tate

CCRi and others

Snowflake Computing Inc.

Initial release

2015

2013

1979

2014

Current release

dBASE 2019, 2019

4.0.5, February 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache 2.0

commercial

Open Source

Apache License 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

Java

Scala

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
OS X

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

yes

predefined 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

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

HTTP REST

none

The IDE can access other DBMS or ODBC-sources.

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

The IDE can access stored procedures in other database systems.

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

none

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

none

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

depending on storage layer

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

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.