DBMS > dBASE vs. Geode vs. QuestDB vs. Snowflake

System Properties Comparison dBASE vs. Geode vs. QuestDB 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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A high performance open source SQL database for time series data

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

Primary database model

Secondary database models

Relational DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	2.70
Rank	#105	Overall
	#8	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

www.dbase.com/support/knowledgebase

geode.apache.org/docs

questdb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

QuestDB Technology Inc

Snowflake Computing Inc.

Initial release

1979

2002

2014

Current release

dBASE 2019, 2019

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 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

Java (Zero-GC), C++, Rust

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

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 query language (OQL)

SQL with time-series extensions

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

.Net
All JVM based languages
C++
Groovy
Java
Scala

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by timestamps)

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication with eventual consistency

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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, on a single node

ACID for single-table writes

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.

yes

through memory mapped files

User concepts

Access control

Access rights for users and roles

Access rights per client and object definable

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

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Fluid real-time dashboards with Grafana and QuestDB
11 June 2024

QuestDB 8.0: Major Release
23 May 2024

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

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.