DBMS > Bangdb vs. GeoMesa vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Realm

System Properties Comparison Bangdb vs. GeoMesa vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Realm

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

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

Primary database model

Document store
Graph DBMS
Time Series DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

bangdb.com

www.geomesa.org

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

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

realm.io

Technical documentation

docs.bangdb.com

www.geomesa.org/documentation/stable/user/index.html

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

realm.io/docs

Developer

Sachin Sinha, BangDB

CCRi and others

Microsoft

Realm, acquired by MongoDB in May 2019

Initial release

2012

2014

2012

1989

2014

Current release

BangDB 2.0, October 2021

4.0.5, February 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache License 2.0

commercial

restricted free version is available

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

C, C++

Scala

C++

Server operating systems

Linux

hosted

Linux
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

APIs and other access methods

Proprietary protocol
RESTful HTTP API

RESTful HTTP API

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

Supported programming languages

C
C#
C++
Java
Python

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

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

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

runs within the applications so server-side scripts are unnecessary

Triggers

yes, Notifications (with Streaming only)

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

depending on storage layer

Sharding

Implicit feature of the cloud service

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

depending on storage layer

yes

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

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

depending on storage layer

yes

In-Memory realm

User concepts

Access control

yes (enterprise version only)

yes

depending on the DBMS used for storage

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

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.