DBMS > Geode vs. HBase vs. Microsoft SQL Server vs. RavenDB

System Properties Comparison Geode vs. HBase vs. Microsoft SQL Server vs. RavenDB

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

geode.apache.org

hbase.apache.org

www.microsoft.com/en-us/sql-server

ravendb.net

Technical documentation

geode.apache.org/docs

hbase.apache.org/book.html

learn.microsoft.com/en-US/sql/sql-server

ravendb.net/docs

Developer

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

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Hibernating Rhinos

Initial release

2002

2008

1989

2010

Current release

1.1, February 2017

2.3.4, January 2021

SQL Server 2022, November 2022

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache version 2

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license 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

Linux
Unix
Windows

using Cygwin

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

schema-free, schema definition possible

yes

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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)

yes

SQL-like query language (RQL)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

Single row ACID (across millions of columns)

ACID

ACID, Cluster-wide transaction available

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.