DBMS > BoltDB vs. jBASE vs. Microsoft Azure AI Search vs. MySQL vs. PostGIS

System Properties Comparison BoltDB vs. jBASE vs. Microsoft Azure AI Search vs. MySQL vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A robust multi-value DBMS comprising development tools and middleware

Search-as-a-service for web and mobile app development

Widely used open source RDBMS

Spatial extension of PostgreSQL

Primary database model

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Vector DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/boltdb/bolt

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

azure.microsoft.com/en-us/services/search

www.mysql.com

postgis.net

Technical documentation

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

learn.microsoft.com/en-us/azure/search

dev.mysql.com/doc

postgis.net/documentation

Developer

Rocket Software (formerly Zumasys)

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

1991

2015

1995

2005

Current release

5.7

8.4.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

optional

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

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Basic
Jabbascript
Java

C#
Java
JavaScript
Python

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

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

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 rights can be defined down to the item level

yes

using Azure authentication

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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.