DBMS > Graph Engine vs. Microsoft Azure SQL Database vs. SQLite vs. STSdb vs. Valentina Server

System Properties Comparison Graph Engine vs. Microsoft Azure SQL Database vs. SQLite vs. STSdb vs. Valentina Server

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used embeddable, in-process RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Object-relational database and reports server

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Key-value store

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.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Score	0.18
Rank	#329	Overall
	#144	Relational DBMS

Website

www.graphengine.io

azure.microsoft.com/en-us/products/azure-sql/database

www.sqlite.org

github.com/STSSoft/STSdb4

www.valentina-db.net

Technical documentation

www.graphengine.io/docs/manual

docs.microsoft.com/en-us/azure/azure-sql

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Microsoft

Dwayne Richard Hipp

STS Soft SC

Paradigma Software

Initial release

2010

2000

2011

1999

Current release

V12

3.45.3 (15 April 2024), April 2024

4.0.8, September 2015

5.7.5

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Public Domain

Open Source

GPLv2, commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

C++

Server operating systems

.NET

hosted

server-less

Windows

Linux
OS X
Windows

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

primitive types and user defined types (classes)

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

SQL-92 is not fully supported

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API

ODBC

Supported programming languages

C#
C++
F#
Visual Basic

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C#
Java

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

Transact SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

via file-system locks

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

User concepts

Access control

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.