DBMS > Geode vs. Microsoft Azure AI Search vs. MySQL vs. Sequoiadb

System Properties Comparison Geode vs. Microsoft Azure AI Search vs. MySQL vs. Sequoiadb

Please select another system to include it in the comparison.

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

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

Widely used open source RDBMS

NewSQL database with distributed OLTP and SQL

Primary database model

Key-value store

Search engine

Relational DBMS

Key/Value like access via memcached API

Document store
Relational DBMS

Secondary database models

Vector DBMS

Document store
Spatial DBMS

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	5.75
Rank	#58	Overall
	#7	Search engines

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.42
Rank	#263	Overall
	#41	Document stores
	#121	Relational DBMS

Website

geode.apache.org

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

www.mysql.com

www.sequoiadb.com

Technical documentation

geode.apache.org/docs

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

dev.mysql.com/doc

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

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

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Sequoiadb Ltd.

Initial release

2002

2015

1995

2013

Current release

1.1, February 2017

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Server: AGPL; Client: Apache V2

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 and C++

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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)

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Supported programming languages

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

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes, on a single node

ACID

not for MyISAM storage engine

Document is locked during a transaction

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

yes

using Azure authentication

Users with fine-grained authorization concept

no user groups or roles

simple password-based access control

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.