DBMS > Amazon Redshift vs. Manticore Search vs. MySQL vs. TDengine

System Properties Comparison Amazon Redshift vs. Manticore Search vs. MySQL vs. TDengine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Multi-storage database for search, including full-text search.

Widely used open source RDBMS

Time Series DBMS and big data platform

Primary database model

Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Website

aws.amazon.com/redshift

manticoresearch.com

www.mysql.com

github.com/taosdata/TDengine
tdengine.com

Technical documentation

docs.aws.amazon.com/redshift

manual.manticoresearch.com

dev.mysql.com/doc

docs.tdengine.com

Developer

Amazon (based on PostgreSQL)

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

TDEngine, previously Taos Data

Initial release

2012

2017

1995

2019

Current release

6.0, February 2023

8.3.0, January 2024

3.0, August 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL V3, also commercial editions available

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

C and C++

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

with proprietary extensions

Standard SQL with extensions for time-series applications

APIs and other access methods

JDBC
ODBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

proprietary syntax

Triggers

yes

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

not for MyISAM storage engine

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

The original contents of fields are not stored in the Manticore 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

Users with fine-grained authorization concept

no user groups or roles

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a next generation data historian purpose-built for Industry 4.0 and...
» more

Competitive advantages

High Performance at any Scale: TDengine is purpose-built for handling massive industrial...
» more

Typical application scenarios

TDengine is designed for Industrial IoT scenarios, including: Manufacturing Connected...
» more

Market metrics

TDengine has garnered over 22,500 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

TDengine OSS is an open source, cloud native time series database. It includes built-in...
» more

News

Compare InfluxDB vs. TDengine
19 April 2024

Why We Need the Next Generation Data Historian
15 April 2024

Is Closed-Source Software Really More Secure?
8 April 2024

Developers: Stop Donating Your Work to Cloud Service Providers!
28 March 2024

Compare AVEVA Data Hub vs. TDengine
19 March 2024

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.