DBMS > GeoSpock vs. Lovefield vs. Microsoft SQL Server vs. Percona Server for MongoDB

System Properties Comparison GeoSpock vs. Lovefield vs. Microsoft SQL Server vs. Percona Server for MongoDB

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

Embeddable relational database for web apps written in pure JavaScript

Microsofts flagship relational DBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Relational DBMS

Document store

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	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

geospock.com

google.github.io/lovefield

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

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

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

docs.percona.com/percona-distribution-for-mongodb

Developer

GeoSpock

Google

Microsoft

Percona

Initial release

2014

1989

2015

Current release

2.0, September 2019

2.1.12, February 2017

SQL Server 2022, November 2022

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

GPL Version 2

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, Javascript

JavaScript

C++

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
Windows

Linux

Data scheme

yes

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

JDBC

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

proprietary protocol using JSON

Supported programming languages

JavaScript

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

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

JavaScript

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

via In-Memory Engine

User concepts

Access control

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

Access rights for users and roles

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.