DBMS > Alibaba Cloud Log Service vs. Amazon DynamoDB vs. Drizzle vs. Google Cloud Datastore vs. Tarantool

System Properties Comparison Alibaba Cloud Log Service vs. Amazon DynamoDB vs. Drizzle vs. Google Cloud Datastore vs. Tarantool

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

A complete real-time data logging service that supports collection, consumption, shipping, search, and analysis of logs.

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Search engine

Document store
Key-value store

Relational DBMS

Document store

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.47
Rank	#263	Overall
	#18	Search engines

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

www.alibabacloud.com/product/log-service

aws.amazon.com/dynamodb

cloud.google.com/datastore

www.tarantool.io

Technical documentation

www.alibabacloud.com/help/en/sls

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

www.tarantool.io/en/doc

Developer

AlibabaCloud Inc.

Amazon

Drizzle project, originally started by Brian Aker

Google

Initial release

2016

2012

2008

Current release

7.2.4, September 2012

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GNU GPL

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

FreeBSD
Linux
OS X

hosted

BSD
Linux
macOS

Data scheme

schema-free

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

yes, details here

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

with proprietary extensions

SQL-like query language (GQL)

Full-featured ANSI SQL support

APIs and other access methods

HTTP REST

RESTful HTTP API

JDBC

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

Open binary protocol

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Java
PHP

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

using Google App Engine

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

3 replicas

yes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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.

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Alibaba Cloud user access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

A real-time service for telementry data (log, metric, trace). Alibaba Cloud Log Service...
» more

Competitive advantages

* Ease of use: Completes data collections from more than 30 data sources within five...
» more

Typical application scenarios

* Log/Trace/Event Search & Analysis * Application Monitoring * Operation Analysis...
» more

Key customers

* Alibaba & Ant-Finance：he infrastructure service for the Corp * Over 22k Subscriber...
» more

Licensing and pricing models

Pay-As-You-Go https://www.alibabacloud.com/product/log-service/pricing
» more

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.