DBMS > Dgraph vs. Firebase Realtime Database vs. HarperDB vs. Microsoft SQL Server

System Properties Comparison Dgraph vs. Firebase Realtime Database vs. HarperDB vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Microsofts flagship relational DBMS

Primary database model

Graph DBMS

Document store

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.39
Rank	#155	Overall
	#15	Graph DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.55
Rank	#243	Overall
	#38	Document stores

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Website

dgraph.io

firebase.google.com/products/realtime-database

www.harperdb.io

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

Technical documentation

dgraph.io/docs

firebase.google.com/docs/database

docs.harperdb.io/docs

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

Developer

Dgraph Labs, Inc.

Google

acquired by Google 2014

HarperDB

Microsoft

Initial release

2016

2012

2017

1989

Current release

3.1, August 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Node.js

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X

Linux
Windows

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data 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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like data manipulation statements

yes

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

Supported programming languages

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

Java
JavaScript
Objective-C

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Custom Functions

since release 3.1

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

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

yes

A table resides as a whole on one (or more) nodes in a cluster

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

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

the nodes on which a table resides can be defined

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

yes, based on authentication and database rules

Access rights for users and roles

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.