DBMS > Galaxybase vs. Microsoft Azure SQL Database vs. SQLite vs. STSdb vs. Warp 10

System Properties Comparison Galaxybase vs. Microsoft Azure SQL Database vs. SQLite vs. STSdb vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Scalable, ACID-compliant native distributed parallel graph platform

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

galaxybase.com

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

www.sqlite.org

github.com/STSSoft/STSdb4

www.warp10.io

Technical documentation

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

www.sqlite.org/docs.html

www.warp10.io/content/02_Getting_started

Developer

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Microsoft

Dwayne Richard Hipp

STS Soft SC

SenX

Initial release

2017

2010

2000

2011

2015

Current release

Nov 20, November 2021

V12

3.46.0 (23 May 2024), May 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

GPLv2, commercial license available

Open Source

Apache License 2.0

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

C and Java

C++

Java

Server operating systems

Linux

hosted

server-less

Windows

Linux
OS X
Windows

Data scheme

Strong typed schema

yes

dynamic column types

yes

schema-free

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

APIs and other access methods

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API

HTTP API
Jupyter
WebSocket

Supported programming languages

Go
Java
Python

.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

Server-side scripts

Stored procedures

user defined procedures and functions

Transact SQL

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Relationships in graphs

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

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

Role-based access control

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.