DBMS > Geode vs. Manticore Search vs. SAP SQL Anywhere vs. SQLite vs. Vitess

System Properties Comparison Geode vs. Manticore Search vs. SAP SQL Anywhere vs. SQLite vs. Vitess

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

Multi-storage database for search, including full-text search.

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

geode.apache.org

manticoresearch.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

vitess.io

Technical documentation

geode.apache.org/docs

manual.manticoresearch.com

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

vitess.io/docs

Developer

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

Manticore Software

SAP

formerly Sybase

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2002

2017

1992

2000

2013

Current release

1.1, February 2017

6.0, February 2023

17, July 2015

3.45.3 (15 April 2024), April 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL version 2

commercial

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses available

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

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Docker
Linux
macOS

Data scheme

schema-free

Fixed schema

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

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

user defined functions

yes, in C/C++, Java, .Net or Perl

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Synchronous replication based on Galera library

Source-replica replication

Database mirroring

none

Multi-source 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 across shards
Immediate Consistency within a shard

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.