DBMS > GridDB vs. Linter vs. Microsoft Azure Cosmos DB vs. TempoIQ

System Properties Comparison GridDB vs. Linter vs. Microsoft Azure Cosmos DB vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

RDBMS for high security requirements

Globally distributed, horizontally scalable, multi-model database service

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Key-value store
Relational DBMS

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.12
Rank	#350	Overall
	#152	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

griddb.net

linter.ru

azure.microsoft.com/services/cosmos-db

tempoiq.com (offline)

Technical documentation

docs.griddb.net

learn.microsoft.com/azure/cosmos-db

Developer

Toshiba Corporation

relex.ru

Microsoft

TempoIQ

Initial release

2013

1990

2014

2012

Current release

5.1, August 2022

License

Commercial or Open Source

Open Source

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

commercial

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

Server operating systems

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP API

Supported programming languages

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

JavaScript

Triggers

yes

JavaScript

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

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

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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