DBMS > Amazon CloudSearch vs. EsgynDB vs. GeoSpock vs. MySQL vs. TinkerGraph

System Properties Comparison Amazon CloudSearch vs. EsgynDB vs. GeoSpock vs. MySQL vs. TinkerGraph

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Search engine

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	1.87
Rank	#140	Overall
	#12	Search engines

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

aws.amazon.com/cloudsearch

www.esgyn.cn

geospock.com

www.mysql.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.aws.amazon.com/cloudsearch

dev.mysql.com/doc

Developer

Amazon

Esgyn

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2015

1995

2009

Current release

2.0, September 2019

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++, Java

Java, Javascript

C and C++

Java

Server operating systems

hosted

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

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

yes

all search fields are automatically indexed

yes

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Groovy
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Automatic sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

optional

In-memory capabilities

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

yes

User concepts

Access control

authentication via encrypted signatures

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or 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.