DBMS > GeoSpock vs. Google Cloud Datastore vs. Memcached vs. Microsoft SQL Server

System Properties Comparison GeoSpock vs. Google Cloud Datastore vs. Memcached vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

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

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Website

geospock.com

cloud.google.com/datastore

www.memcached.org

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

Technical documentation

cloud.google.com/datastore/docs

github.com/memcached/memcached/wiki

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

Developer

GeoSpock

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Initial release

2008

2003

1989

Current release

2.0, September 2019

1.6.29, June 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

restricted free version is 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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java, Javascript

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Proprietary protocol

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

Supported programming languages

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

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

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

Server-side scripts

Stored procedures

using Google App Engine

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

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

User concepts

Access control

Access rights for users can be defined per table

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

using SASL (Simple Authentication and Security Layer) protocol

fine grained access rights according to SQL-standard

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.