DBMS > Graph Engine vs. Graphite vs. MarkLogic vs. Microsoft SQL Server

System Properties Comparison Graph Engine vs. Graphite vs. MarkLogic vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Operational and transactional Enterprise NoSQL database

Microsofts flagship relational DBMS

Primary database model

Graph DBMS
Key-value store

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.graphengine.io

github.com/graphite-project/graphite-web

www.marklogic.com

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

Technical documentation

www.graphengine.io/docs/manual

graphite.readthedocs.io

docs.marklogic.com

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

Developer

Microsoft

Chris Davis

MarkLogic Corp.

Microsoft

Initial release

2010

2006

2001

1989

Current release

11.0, December 2022

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

restricted free version is available

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

.NET and C

Python

C++

Server operating systems

.NET

Linux
Unix

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

yes

SQL92

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

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

Supported programming languages

C#
C++
F#
Visual Basic

JavaScript (Node.js)
Python

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

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

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

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.