DBMS > Amazon Redshift vs. Manticore Search vs. TimesTen vs. VelocityDB

System Properties Comparison Amazon Redshift vs. Manticore Search vs. TimesTen vs. VelocityDB

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.

In-Memory RDBMS compatible to Oracle

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Search engine

Relational DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

manticoresearch.com

www.oracle.com/database/technologies/related/timesten.html

velocitydb.com

Technical documentation

docs.aws.amazon.com/redshift

manual.manticoresearch.com

docs.oracle.com/database/timesten-18.1

velocitydb.com/UserGuide

Developer

Amazon (based on PostgreSQL)

Manticore Software

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

VelocityDB Inc

Initial release

2012

2017

1998

2011

Current release

6.0, February 2023

11 Release 2 (11.2.2.8.0)

7.x

License

Commercial or Open Source

commercial

Open Source

GPL version 2

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
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Any that supports .NET

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

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

APIs and other access methods

JDBC
ODBC

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.Net

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Java
PL/SQL

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

PL/SQL

Triggers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

by means of logfiles and checkpoints

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

Based on Windows Authentication

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.