DBMS > Amazon CloudSearch vs. GridDB vs. Percona Server for MySQL vs. SQLite

System Properties Comparison Amazon CloudSearch vs. GridDB vs. Percona Server for MySQL vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Scalable in-memory time series database optimized for IoT and Big Data

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Widely used embeddable, in-process RDBMS

Primary database model

Search engine

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	1.86
Rank	#133	Overall
	#12	Search engines

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	2.06
Rank	#118	Overall
	#57	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/cloudsearch

griddb.net

www.percona.com/software/mysql-database/percona-server

www.sqlite.org

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.griddb.net

www.percona.com/downloads/Percona-Server-LATEST

www.sqlite.org/docs.html

Developer

Amazon

Toshiba Corporation

Percona

Dwayne Richard Hipp

Initial release

2012

2013

2008

2000

Current release

5.1, August 2022

8.0.36-28, 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

GPL version 2

Open Source

Public Domain

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

C++

C and C++

Server operating systems

hosted

Linux

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Source-replica replication

Multi-source replication
Source-replica replication
XtraDB Cluster

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

authentication via encrypted signatures

Access rights for users can be defined per database

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.