DBMS > Graph Engine vs. Microsoft SQL Server vs. Percona Server for MySQL vs. PouchDB vs. SWC-DB

System Properties Comparison Graph Engine vs. Microsoft SQL Server vs. Percona Server for MySQL vs. PouchDB vs. SWC-DB

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

Microsofts flagship relational DBMS

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

JavaScript DBMS with an API inspired by CouchDB

A high performance, scalable Wide Column DBMS

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Document store

Wide column store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Time Series 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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

www.graphengine.io

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

www.percona.com/software/mysql-database/percona-server

pouchdb.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.graphengine.io/docs/manual

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

www.percona.com/downloads/Percona-Server-LATEST

pouchdb.com/guides

Developer

Microsoft

Percona

Apache Software Foundation

Alex Kashirin

Initial release

2010

1989

2008

2012

2020

Current release

SQL Server 2022, November 2022

8.0.36-28, 2024

7.1.1, June 2019

0.5, April 2021

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

GPL version 2

Open Source

GPL V3

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

C++

C and C++

JavaScript

C++

Server operating systems

.NET

Linux
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

via views

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

ADO.NET
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

Proprietary protocol
Thrift

Supported programming languages

C#
C++
F#
Visual Basic

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript

C++

Server-side scripts

Stored procedures

yes

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

yes

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

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

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication
XtraDB Cluster

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.