DBMS > Amazon SimpleDB vs. Google Cloud Datastore vs. LokiJS vs. MySQL vs. Solr

System Properties Comparison Amazon SimpleDB vs. Google Cloud Datastore vs. LokiJS vs. MySQL vs. Solr

Editorial information provided by DB-Engines

Name

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

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

In-memory JavaScript DBMS

Widely used open source RDBMS

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	1.85
Rank	#138	Overall
	#24	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

aws.amazon.com/simpledb

cloud.google.com/datastore

github.com/techfort/LokiJS

www.mysql.com

solr.apache.org

Technical documentation

docs.aws.amazon.com/simpledb

cloud.google.com/datastore/docs

techfort.github.io/LokiJS

dev.mysql.com/doc

solr.apache.org/resources.html

Developer

Amazon

Google

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Initial release

2007

2008

2014

1995

2006

Current release

8.4.0, April 2024

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 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.

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

Implementation language

JavaScript

C and C++

Java

Server operating systems

hosted

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

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes, details here

yes

supports customizable data types and automatic typing

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 columns are indexed automatically

yes

via views

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP API

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

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

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

JavaScript

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

using Google App Engine

View functions in JavaScript

yes

proprietary syntax

Java plugins

Triggers

Callbacks using the Google Apps Engine

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

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.

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

Concurrent data updates can be detected by the application

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a single collection possible

ACID

not for MyISAM storage engine

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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 and roles can be defined via the AWS Identity and Access Management (IAM)

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

Users with fine-grained authorization concept

no user groups or roles

yes

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.