DBMS > dBASE vs. Hazelcast vs. Snowflake vs. Sphinx

System Properties Comparison dBASE vs. Hazelcast vs. Snowflake vs. Sphinx

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.

A widely adopted in-memory data grid

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

Technical documentation

www.dbase.com/support/knowledgebase

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Asthon Tate

Hazelcast

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

1979

2008

2014

2001

Current release

dBASE 2019, 2019

5.3.6, November 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

All OS with a Java VM

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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

yes

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

dBase proprietary IDE

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Role-based access control

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.