DBMS > FatDB vs. GridDB vs. OpenQM vs. SpatiaLite

System Properties Comparison FatDB vs. GridDB vs. OpenQM 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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Time Series DBMS

Multivalue DBMS

Spatial DBMS

Secondary database models

Key-value store
Relational DBMS

Relational DBMS

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

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

griddb.net

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

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

Technical documentation

docs.griddb.net

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

Developer

FatCloud

Toshiba Corporation

Rocket Software, originally Martin Phillips

Alessandro Furieri

Initial release

2012

2013

1993

2008

Current release

5.1, August 2022

3.4-12

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

GPLv2, extended commercial license available

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

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less

Data scheme

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL92, SQL-like TQL (Toshiba 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

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights can be defined down to the item level

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.

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

General Availability of GridDB® 5.5 Enterprise Edition ~Enhancing the efficiency of IoT system development and ...
16 January 2024, global.toshiba

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

GridDB Use case Large-scale high-speed processing of smart meter data following the deregulation of electrical power ...
1 November 2020, global.toshiba

Toshiba's Distributed Database GridDB(R) Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data ...
3 December 2019, global.toshiba

General Availability of GridDB 5.1 Enterprise Edition ~ Continuous database usage in the event of data center failure ...
19 August 2022, global.toshiba

provided by Google News

Share this page