DBMS > Google Cloud Datastore vs. Manticore Search vs. MarkLogic vs. Redis vs. Teradata Aster

System Properties Comparison Google Cloud Datastore vs. Manticore Search vs. MarkLogic vs. Redis vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

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

Operational and transactional Enterprise NoSQL database

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store

Search engine

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Website

cloud.google.com/datastore

manticoresearch.com

www.marklogic.com

redis.com
redis.io

Technical documentation

cloud.google.com/datastore/docs

manual.manticoresearch.com

docs.marklogic.com

docs.redis.com/latest/index.html
redis.io/docs

Developer

Google

Manticore Software

MarkLogic Corp.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Teradata

Initial release

2008

2017

2001

2009

2005

Current release

6.0, February 2023

11.0, December 2022

7.2.5, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

restricted free version is available

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

C++

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

schema-free

Fixed schema

schema-free

Schema can be enforced

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes, details here

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

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

in Aster File Store

Secondary indexes

yes

full-text index on all search fields

yes

with RediSearch module

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

yes

SQL92

with RediSQL module

yes

APIs and other access methods

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

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

yes

via XQuery or JavaScript

Lua; Redis Functions coming in Redis 7 (slides and Github)

R packages

Triggers

Callbacks using the Google Apps Engine

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Synchronous replication based on Galera library

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

through RedisGears

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Immediate Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

can act as a resource manager in an XA/JTA transaction

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

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

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

yes, with Range Indexes

yes

User concepts

Access control

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

Role-based access control at the document and subdocument levels

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

fine grained access rights according to SQL-standard

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.