DBMS > HBase vs. InfinityDB vs. SQLite vs. Vitess

System Properties Comparison HBase vs. InfinityDB vs. SQLite vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A Java embedded Key-Value Store which extends the Java Map interface

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Wide column store

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

Technical documentation

hbase.apache.org/book.html

boilerbay.com/infinitydb/manual

www.sqlite.org/docs.html

vitess.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Boiler Bay Inc.

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2008

2002

2000

2013

Current release

2.3.4, January 2021

4.0

3.46.0 (23 May 2024), May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

Linux
Unix
Windows

using Cygwin

All OS with a Java VM

server-less

Docker
Linux
macOS

Data scheme

schema-free, schema definition possible

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

dynamic column types

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
Thrift

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

Java

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

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

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.