DBMS > FatDB vs. Memcached vs. Microsoft SQL Server vs. Teradata Aster vs. TigerGraph

System Properties Comparison FatDB vs. Memcached vs. Microsoft SQL Server vs. Teradata Aster vs. TigerGraph

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.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

In-memory key-value store, originally intended for caching

Microsofts flagship relational DBMS

Platform for big data analytics on multistructured data sources and types

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

www.memcached.org

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

www.tigergraph.com

Technical documentation

github.com/memcached/memcached/wiki

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

docs.tigergraph.com

Developer

FatCloud

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Teradata

Initial release

2012

2003

1989

2005

2017

Current release

1.6.25, March 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

restricted free version is available

commercial

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

C++

Server operating systems

Windows

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL-like query language (GSQL)

APIs and other access methods

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

Proprietary protocol

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

ADO.NET
JDBC
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

C
C#
C++
Java
Python
R

C++
Java

Server-side scripts

Stored procedures

yes

via applications

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

R packages

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

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

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

Can implement custom security layer via applications

yes

using SASL (Simple Authentication and Security Layer) protocol

fine grained access rights according to SQL-standard

Role-based access control

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.