DBMS > HBase vs. Microsoft Access vs. Oracle Berkeley DB vs. RocksDB vs. Sphinx

System Properties Comparison HBase vs. Microsoft Access vs. Oracle Berkeley DB vs. RocksDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Widely used in-process key-value store

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

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

Primary database model

Wide column store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Search engine

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

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

hbase.apache.org

www.microsoft.com/en-us/microsoft-365/access

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

sphinxsearch.com

Technical documentation

hbase.apache.org/book.html

developer.microsoft.com/en-us/access

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2008

1992

1994

2013

2001

Current release

2.3.4, January 2021

1902 (16.0.11328.20222), March 2019

18.1.40, May 2020

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

Open Source

commercial license available

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Windows

Not a real database server, but making use of DLLs

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free, schema definition possible

yes

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

only with the Berkeley DB XML edition

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL interfaced based on SQLite is available

SQL-like query language (SphinxQL)

APIs and other access methods

Java API
RESTful HTTP API
Thrift

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Proprietary protocol

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

but no files for transaction logging

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

a simple user-level security was built in till version Access 2003

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.