DBMS > BigchainDB vs. GeoMesa vs. JaguarDB vs. SQLite vs. Tibero

System Properties Comparison BigchainDB vs. GeoMesa vs. JaguarDB vs. SQLite vs. Tibero

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Performant, highly scalable DBMS for AI and IoT applications

Widely used embeddable, in-process RDBMS

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store

Spatial DBMS

Key-value store
Vector DBMS

Relational DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

us.tmaxsoft.com/products/tibero

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.geomesa.org/documentation/stable/user/index.html

www.jaguardb.com/support.html

www.sqlite.org/docs.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

CCRi and others

DataJaguar, Inc.

Dwayne Richard Hipp

TmaxSoft

Initial release

2016

2014

2015

2000

2003

Current release

5.0.0, May 2024

3.3 July 2023

3.46.0 (23 May 2024), May 2024

6, April 2015

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache License 2.0

Open Source

GPL V3.0

Open Source

Public Domain

commercial

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

Python

Scala

C++

the server part. Clients available in other languages

C and Assembler

Server operating systems

Linux

server-less

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-92 is not fully supported

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

none

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

Multi-source 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

depending on storage layer

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

planned for next version

User concepts

Access control

yes

depending on the DBMS used for storage

rights management via user accounts

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.