DBMS > Amazon CloudSearch vs. EXASOL vs. GeoSpock vs. Lovefield vs. Microsoft SQL Server

System Properties Comparison Amazon CloudSearch vs. EXASOL vs. GeoSpock vs. Lovefield vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

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

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Spatial and temporal data processing engine for extreme data scale

Embeddable relational database for web apps written in pure JavaScript

Microsofts flagship relational DBMS

Primary database model

Search engine

Relational DBMS

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	1.87
Rank	#140	Overall
	#12	Search engines

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

aws.amazon.com/cloudsearch

www.exasol.com

geospock.com

google.github.io/lovefield

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

Technical documentation

docs.aws.amazon.com/cloudsearch

www.exasol.com/resources

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

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

Developer

Amazon

Exasol

GeoSpock

Google

Microsoft

Initial release

2012

2000

2014

1989

Current release

2.0, September 2019

2.1.12, February 2017

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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.

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

Data scheme

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

all search fields are automatically indexed

yes

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

HTTP API

.Net
JDBC
ODBC
WebSocket

JDBC

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

Supported programming languages

Java
Lua
Python
R

JavaScript

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

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Automatic sharding

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

none

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

User concepts

Access control

authentication via encrypted signatures

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per table

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.