DBMS > FatDB vs. GridDB vs. Manticore Search vs. SpatiaLite

System Properties Comparison FatDB vs. GridDB vs. Manticore Search vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

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

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Time Series DBMS

Search engine

Spatial DBMS

Secondary database models

Key-value store
Relational DBMS

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS

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

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Website

griddb.net

manticoresearch.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

docs.griddb.net

manual.manticoresearch.com

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

FatCloud

Toshiba Corporation

Manticore Software

Alessandro Furieri

Initial release

2012

2013

2017

2008

Current release

5.1, August 2022

6.0, February 2023

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

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

Open Source

GPL version 2

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Cloud-based only

Only available as a cloud 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

Windows

Linux

FreeBSD
Linux
macOS
Windows

server-less

Data scheme

schema-free

yes

Fixed schema

yes

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

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

Via inetgration in SQL Server

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

Supported programming languages

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

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

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Synchronous replication based on Galera library

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Eventual Consistency
Immediate Consistency

Immediate consistency within container, eventual consistency across containers

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

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

Can implement custom security layer via applications

Access rights for users can be defined per database

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

TOSHIBA DIGITAL SOLUTIONS CORPORATION
1 November 2020, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data Management
3 December 2019, global.toshiba

Amazon Proposes to Develop New Data Center Campus in Virginia
26 August 2022, w.media

’s SQL Interface, Aims to Accelerate Open Innovation
17 June 2020, global.toshiba

provided by Google News

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

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

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

Highlighting in Search Results
24 May 2020, hackernoon.com

40 Stories To Learn About Elasticsearch
27 April 2023, hackernoon.com

provided by Google News

Share this page