DBMS > Apache Phoenix vs. FatDB vs. Microsoft SQL Server vs. SwayDB

System Properties Comparison Apache Phoenix vs. FatDB vs. Microsoft SQL Server vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Microsofts flagship relational DBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

phoenix.apache.org

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

swaydb.simer.au

Technical documentation

phoenix.apache.org

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

Developer

Apache Software Foundation

FatCloud

Microsoft

Simer Plaha

Initial release

2014

2012

1989

2018

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

GNU Affero GPL V3.0

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.

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

Java

C++

Scala

Server operating systems

Linux
Unix
Windows

Windows

Linux
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

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

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

yes

via applications

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

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of operations

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.

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Can implement custom security layer via applications

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.