DBMS > PlanetScale vs. PostGIS vs. Stardog vs. VelocityDB

System Properties Comparison PlanetScale vs. PostGIS vs. Stardog vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Spatial DBMS

Graph DBMS
RDF store

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

Technical documentation

planetscale.com/docs

postgis.net/documentation

docs.stardog.com

velocitydb.com/UserGuide

Developer

PlanetScale

Stardog-Union

VelocityDB Inc

Initial release

2020

2005

2010

2011

Current release

3.4.2, February 2024

7.3.0, May 2020

7.x

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Server operating systems

Docker
Linux
macOS

Linux
macOS
Windows

Any that supports .NET

Data scheme

yes

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

.Net

Supported programming languages

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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

relationships in graphs

Transaction concepts

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

Access rights for users and roles

Based on Windows Authentication

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
1 June 2024, Yahoo Movies Canada

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, Business Wire

How to Migrate to PlanetScale's Serverless Database
14 October 2021, The New Stack

provided by Google News

Share this page