DBMS > Geode vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. OpenEdge vs. Realm

System Properties Comparison Geode vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. OpenEdge vs. Realm

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 Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

Application development environment with integrated database management system

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	4.92
Rank	#73	Overall
	#6	Wide column stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	3.75
Rank	#88	Overall
	#47	Relational DBMS

Score	7.71
Rank	#52	Overall
	#9	Document stores

Website

geode.apache.org

azure.microsoft.com/en-us/services/storage/tables

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

www.progress.com/openedge

realm.io

Technical documentation

geode.apache.org/docs

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

documentation.progress.com/output/ua/OpenEdge_latest

realm.io/docs

Developer

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

Microsoft

Progress Software Corporation

Realm, acquired by MongoDB in May 2019

Initial release

2002

2012

1989

1984

2014

Current release

1.1, February 2017

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

commercial

Open Source

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

hosted

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

close to SQL 92

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

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

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

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

Progress proprietary ABL (Advanced Business Language)

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

user defined functions

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

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Cache Event Listeners

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

optimistic locking

ACID

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

In-Memory realm

User concepts

Access control

Access rights per client and object definable

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Users and groups

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.