DBMS > GridGain vs. Microsoft Azure SQL Database vs. Valentina Server

System Properties Comparison GridGain vs. Microsoft Azure SQL Database vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

Database as a Service offering with high compatibility to Microsoft SQL Server

Object-relational database and reports server

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.92
Rank	#126	Overall
	#25	Key-value stores
	#62	Relational DBMS

Score	86.01
Rank	#15	Overall
	#10	Relational DBMS

Score	0.19
Rank	#289	Overall
	#136	Relational DBMS

Website

www.gridgain.com

azure.microsoft.com/en-us/services/sql-database

www.valentina-db.net

Technical documentation

www.gridgain.com/docs/latest

docs.microsoft.com/en-us/azure/azure-sql

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

GridGain Systems, Inc.

Microsoft

Paradigma Software

Initial release

2007

2010

1999

Current release

GridGain 8.5.1

V12

5.7.5

License

Commercial or Open Source

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

Java, C++, .Net

C++

Server operating systems

Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

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

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC

ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

Transact SQL

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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