DBMS > JaguarDB vs. PlanetScale vs. PostGIS vs. Riak TS

System Properties Comparison JaguarDB vs. PlanetScale vs. PostGIS vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

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

Spatial extension of PostgreSQL

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Key-value store
Vector DBMS

Relational DBMS

Spatial DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

www.jaguardb.com

planetscale.com

postgis.net

Technical documentation

www.jaguardb.com/support.html

planetscale.com/docs

postgis.net/documentation

www.tiot.jp/riak-docs/riak/ts/latest

Developer

DataJaguar, Inc.

PlanetScale

Open Source, formerly Basho Technologies

Initial release

2015

2020

2005

2015

Current release

3.3 July 2023

3.4.2, February 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

GPL V3.0

commercial

Open Source

GPL v2.0

Open Source

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

the server part. Clients available in other languages

Erlang

Server operating systems

Linux

Docker
Linux
macOS

Linux
OS X

Data scheme

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

restricted

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

yes

yes, limited

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

links between datasets can be stored

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

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

provided by Google News

Share this page