DBMS > Google Cloud Datastore vs. Manticore Search vs. SAP HANA vs. SurrealDB

System Properties Comparison Google Cloud Datastore vs. Manticore Search vs. SAP HANA vs. SurrealDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

In-memory, column based data store. Available as appliance or cloud service

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Document store

Search engine

Relational DBMS

Document store
Graph DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

cloud.google.com/datastore

manticoresearch.com

www.sap.com/products/hana.html

surrealdb.com

Technical documentation

cloud.google.com/datastore/docs

manual.manticoresearch.com

help.sap.com/hana

surrealdb.com/docs

Developer

Google

Manticore Software

SAP

SurrealDB Ltd

Initial release

2008

2017

2010

2022

Current release

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

v1.5.0, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

Open Source

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Rust

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Appliance or cloud-service

Linux
macOS
Windows

Data scheme

schema-free

Fixed schema

yes

schema-free

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

SQL-like query language

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

JDBC
ODBC

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

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

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

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Synchronous replication based on Galera library

yes

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

yes

User concepts

Access control

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

yes

yes, based on authentication and database rules

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.