DBMS > Dgraph vs. InfinityDB vs. Microsoft SQL Server vs. OrigoDB

System Properties Comparison Dgraph vs. InfinityDB vs. Microsoft SQL Server vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A Java embedded Key-Value Store which extends the Java Map interface

Microsofts flagship relational DBMS

A fully ACID in-memory object graph database

Primary database model

Graph DBMS

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

dgraph.io

boilerbay.com

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

origodb.com

Technical documentation

dgraph.io/docs

boilerbay.com/infinitydb/manual

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

origodb.com/docs

Developer

Dgraph Labs, Inc.

Boiler Bay Inc.

Microsoft

Robert Friberg et al

Initial release

2016

2002

1989

2009

under the name LiveDB

Current release

4.0

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

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

Java

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
Windows

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

APIs and other access methods

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

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

.NET Client API
HTTP API
LINQ

Supported programming languages

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

Java

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

.Net

Server-side scripts

Stored procedures

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

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

yes

none

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

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

depending on model

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Role based authorization

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.