DBMS > Geode vs. jBASE vs. Microsoft Azure AI Search vs. mSQL vs. RocksDB

System Properties Comparison Geode vs. jBASE vs. Microsoft Azure AI Search vs. mSQL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A robust multi-value DBMS comprising development tools and middleware

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

Primary database model

Secondary database models

Vector DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

geode.apache.org

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

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

hughestech.com.au/products/msql

rocksdb.org

Technical documentation

geode.apache.org/docs

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

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

github.com/facebook/rocksdb/wiki

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Rocket Software (formerly Zumasys)

Microsoft

Hughes Technologies

Facebook, Inc.

Initial release

2002

1991

2015

1994

2013

Current release

1.1, February 2017

5.7

4.4, October 2021

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free licenses can be provided

Open Source

BSD

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.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Linux
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

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

SQL-like query language (OQL)

Embedded SQL for jBASE in BASIC

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

RESTful HTTP API

JDBC
ODBC

C++ API
Java API

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Basic
Jabbascript
Java

C#
Java
JavaScript
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

ACID

yes

Concurrency

Support for concurrent manipulation of data

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 per client and object definable

Access rights can be defined down to the item level

yes

using Azure authentication

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.