DBMS > Geode vs. IBM Cloudant vs. Solr vs. SQLite

System Properties Comparison Geode vs. IBM Cloudant vs. Solr vs. SQLite

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

Database as a Service offering based on Apache CouchDB

A widely used distributed, scalable search engine based on Apache Lucene

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

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

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

www.ibm.com/products/cloudant

solr.apache.org

www.sqlite.org

Technical documentation

geode.apache.org/docs

cloud.ibm.com/docs/Cloudant

solr.apache.org/resources.html

www.sqlite.org/docs.html

Developer

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

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2002

2010

2006

2000

Current release

1.1, February 2017

9.6.1, May 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Apache Version 2

Open Source

Public Domain

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

Erlang

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

server-less

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

dynamic column types

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes

not rigid because of 'dynamic typing' concept.

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
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

Server-side scripts

Stored procedures

user defined functions

View functions (Map-Reduce) in JavaScript

Java plugins

Triggers

yes

Cache Event Listeners

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

atomic operations within a document possible

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

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 for users can be defined per database

yes

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.