DBMS > Alibaba Cloud AnalyticDB for MySQL vs. Google Cloud Datastore vs. Sphinx vs. SQLite vs. TempoIQ

System Properties Comparison Alibaba Cloud AnalyticDB for MySQL vs. Google Cloud Datastore vs. Sphinx vs. SQLite vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A real-time data warehousing service that can process petabytes of data with high concurrency and low latency. It is fully compatible with the MySQL protocol.

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

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Secondary database models

Document store

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

Score	0.85
Rank	#207	Overall
	#96	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.alibabacloud.com/product/analyticdb-for-mysql

cloud.google.com/datastore

sphinxsearch.com

www.sqlite.org

tempoiq.com (offline)

Technical documentation

www.alibabacloud.com/help/doc-detail/93776.htm

cloud.google.com/datastore/docs

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Alibaba

Google

Sphinx Technologies Inc.

Dwayne Richard Hipp

TempoIQ

Initial release

2008

2001

2000

2012

Current release

3.5.1, February 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

commercial

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++

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

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

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

C#
Java
PHP
Python

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

fine grained access rights according to SQL-standard

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

simple authentication-based access control

More information provided by the system vendor

Specific characteristics

A real-time data warehousing service that can process PB data with high concurrency...
» more

Competitive advantages

TPC Benchmark: The world leading result in TPC-DS benchmark . TPC-H benchmark for...
» more

Licensing and pricing models

Available regions: America US Virginia US Silicon Valley Asia China Hong Kong India...
» 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.