DBMS > Dgraph vs. Google Cloud Datastore vs. InterSystems IRIS vs. Microsoft SQL Server vs. Newts

System Properties Comparison Dgraph vs. Google Cloud Datastore vs. InterSystems IRIS vs. Microsoft SQL Server vs. Newts

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A containerised multi-model DBMS, interoperability and analytics data platform with wide capabilities for vertical and horizontal scalability

Microsofts flagship relational DBMS

Time Series DBMS based on Cassandra

Primary database model

Graph DBMS

Document store

Document store
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	4.39
Rank	#81	Overall
	#13	Document stores
	#10	Key-value stores
	#1	Object oriented DBMS
	#44	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Website

dgraph.io

cloud.google.com/datastore

www.intersystems.com/products/intersystems-iris

www.microsoft.com/en-us/sql-server

opennms.github.io/newts

Technical documentation

dgraph.io/docs

cloud.google.com/datastore/docs

docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls

learn.microsoft.com/en-US/sql/sql-server

github.com/OpenNMS/newts/wiki

Developer

Dgraph Labs, Inc.

Google

InterSystems

Microsoft

OpenNMS Group

Initial release

2016

2008

2018

1989

2014

Current release

2023.3, June 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

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

Java

Server operating systems

Linux
OS X
Windows

hosted

AIX
Linux
macOS
Ubuntu
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

depending on used data model

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST
Java API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C++
Java
JavaScript (Node.js)
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java

Server-side scripts

Stored procedures

using Google App Engine

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication using Paxos

Source-replica replication

yes, but depending on the SQL-Server Edition

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

InterSystems IRIS is a complete cloud-first data platform which includes a multi-model...
» 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.