DBMS > Kingbase vs. Memcached vs. Microsoft SQL Server vs. TigerGraph vs. Yanza

System Properties Comparison Kingbase vs. Memcached vs. Microsoft SQL Server vs. TigerGraph vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

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

Microsofts flagship relational DBMS

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

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

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.kingbase.com.cn

www.memcached.org

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

www.tigergraph.com

yanza.com

Technical documentation

github.com/memcached/memcached/wiki

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

docs.tigergraph.com

Developer

BeiJing KINGBASE Information technologies inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Yanza

Initial release

1999

2003

1989

2017

2015

Current release

V8.0, August 2021

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

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and Java

C++

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

Linux

Windows

Data scheme

yes

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

Standard with numerous extensions

yes

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

Proprietary protocol

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

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

HTTP API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.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++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

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

yes

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

fine grained access rights according to SQL-standard

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.