DBMS > Brytlyt vs. HBase vs. SpatiaLite vs. SQLite

System Properties Comparison Brytlyt vs. HBase vs. SpatiaLite vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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

Spatial extension of SQLite

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

hbase.apache.org

www.gaia-gis.it/fossil/libspatialite/index

www.sqlite.org

Technical documentation

docs.brytlyt.io

hbase.apache.org/book.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.sqlite.org/docs.html

Developer

Brytlyt

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Alessandro Furieri

Dwayne Richard Hipp

Initial release

2016

2008

2000

Current release

5.0, August 2023

2.3.4, January 2021

5.0.0, August 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Public Domain

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

C, C++ and CUDA

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
Unix
Windows

using Cygwin

server-less

Data scheme

yes

schema-free, schema definition possible

yes

dynamic column types

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

yes

not rigid because of 'dynamic typing' concept.

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API
RESTful HTTP API
Thrift

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

fine grained access rights according to SQL-standard

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.