DBMS > GeoMesa vs. Memcached vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. YDB

System Properties Comparison GeoMesa vs. Memcached vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. YDB

Editorial information provided by DB-Engines

Name

Description

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

In-memory key-value store, originally intended for caching

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

Microsofts flagship relational DBMS

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

www.geomesa.org

www.memcached.org

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

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

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

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

github.com/memcached/memcached/wiki

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

ydb.tech/en/docs

Developer

CCRi and others

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Yandex

Initial release

2014

2003

2012

1989

2019

Current release

4.0.5, February 2024

1.6.25, March 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD license

commercial

restricted free version is available

Open Source

Apache 2.0; commercial license available

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

Scala

C++

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux
Windows

Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

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

yes

SQL-like query language (YQL)

APIs and other access methods

Proprietary protocol

RESTful HTTP API

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

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Implicit feature of the cloud service

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Repcached, a Memcached patch, provides this functionallity

yes

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

yes, but depending on the SQL-Server Edition

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Access rights defined for Yandex Cloud users

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.