DBMS > GridDB vs. Manticore Search vs. SAP HANA vs. Sequoiadb

System Properties Comparison GridDB vs. Manticore Search vs. SAP HANA vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

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

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

NewSQL database with distributed OLTP and SQL

Primary database model

Time Series DBMS

Search engine

Relational DBMS

Document store
Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Website

griddb.net

manticoresearch.com

www.sap.com/products/hana.html

www.sequoiadb.com

Technical documentation

docs.griddb.net

manual.manticoresearch.com

help.sap.com/hana

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Toshiba Corporation

Manticore Software

SAP

Sequoiadb Ltd.

Initial release

2013

2017

2010

2013

Current release

5.1, August 2022

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

GPL version 2

commercial

Open Source

Server: AGPL; Client: Apache V2

Cloud-based only

Only available as a cloud service

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

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

Appliance or cloud-service

Linux

Data scheme

yes

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

yes

oid, date, timestamp, binary, regex

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

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

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

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication based on Galera library

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Document is locked during a transaction

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 can be defined per database

yes

simple password-based access control

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.