DBMS > Dgraph vs. GeoMesa vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. Solr

System Properties Comparison Dgraph vs. GeoMesa vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. Solr

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Microsofts flagship relational DBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial 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.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

dgraph.io

www.geomesa.org

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

www.sap.com/products/technology-platform/sql-anywhere.html

solr.apache.org

Technical documentation

dgraph.io/docs

www.geomesa.org/documentation/stable/user/index.html

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

help.sap.com/docs/SAP_SQL_Anywhere

solr.apache.org/resources.html

Developer

Dgraph Labs, Inc.

CCRi and others

Microsoft

SAP

formerly Sybase

Apache Software Foundation

Initial release

2016

2014

1989

1992

2006

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

17, July 2015

9.5.0, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

Open Source

Apache Version 2

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

Scala

C++

Java

Server operating systems

Linux
OS X
Windows

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

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

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

ADO.NET
HTTP API
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

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

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

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

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

yes, in C/C++, Java, .Net or Perl

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

yes

depending on storage layer

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

depending on storage layer

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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.

depending on storage layer

yes

User concepts

Access control

Planned for future releases

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes

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.