DBMS > Google Cloud Datastore vs. Manticore Search vs. Trafodion

System Properties Comparison Google Cloud Datastore vs. Manticore Search vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded 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.

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

Search engine

Relational 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	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

cloud.google.com/datastore

manticoresearch.com

trafodion.apache.org

Technical documentation

cloud.google.com/datastore/docs

manual.manticoresearch.com

trafodion.apache.org/documentation.html

Developer

Google

Manticore Software

Apache Software Foundation, originally developed by HP

Initial release

2008

2017

2014

Current release

6.0, February 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache 2.0

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

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Linux

Data scheme

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes, details here

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

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

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

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

Java Stored Procedures

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Synchronous replication based on Galera library

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via user defined functions and HBase

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

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

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

In-memory capabilities

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

User concepts

Access control

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
29 April 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

What Is Google Cloud Platform?
28 August 2023, Simplilearn

provided by Google News

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

Google's Gemini comes to databases
9 April 2024, Yahoo Canada Shine On

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

provided by Google News

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

HP Throws Trafodion Hat into OLTP Hadoop Ring
14 July 2014, Datanami

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page