DBMS > Kyligence Enterprise vs. Microsoft Azure SQL Database vs. PlanetScale vs. SQLite vs. Valentina Server

System Properties Comparison Kyligence Enterprise vs. Microsoft Azure SQL Database vs. PlanetScale vs. SQLite vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, built on top of Apache Kylin

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

kyligence.io/kyligence-enterprise

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

planetscale.com

www.sqlite.org

www.valentina-db.net

Technical documentation

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

planetscale.com/docs

www.sqlite.org/docs.html

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

Developer

Kyligence, Inc.

Microsoft

PlanetScale

Dwayne Richard Hipp

Paradigma Software

Initial release

2016

2010

2020

2000

1999

Current release

V12

3.45.3 (15 April 2024), April 2024

5.7.5

License

Commercial or Open Source

commercial

Open Source

Public Domain

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

Java

C++

Server operating systems

Linux

hosted

Docker
Linux
macOS

server-less

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

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

ANSI SQL for queries (using Apache Calcite)

yes

with proprietary extensions

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

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

Server-side scripts

Stored procedures

Transact SQL

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

via file-system locks

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

Users with fine-grained authorization concept

no user groups or roles

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.