DBMS > Linter vs. PlanetScale vs. RocksDB vs. TypeDB

System Properties Comparison Linter vs. PlanetScale vs. RocksDB vs. TypeDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

RDBMS for high security requirements

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

TypeDB is a strongly-typed database with a rich and logical type system and TypeQL as its query language

Primary database model

Relational DBMS

Key-value store

Graph DBMS
Relational DBMS

Often described as a 'hyper-relational' database, since it implements the 'Entity-Relationship Paradigm' to manage complex data structures and ontologies.

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.65
Rank	#234	Overall
	#20	Graph DBMS
	#107	Relational DBMS

Website

Technical documentation

planetscale.com/docs

github.com/facebook/rocksdb/wiki

typedb.com/docs

Developer

relex.ru

PlanetScale

Facebook, Inc.

Vaticle

Initial release

1990

2020

2013

2016

Current release

8.11.4, April 2024

2.26.3, January 2024

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL Version 3, commercial licenses available

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

C++

Java

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Docker
Linux
macOS

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (Visualisation software- previously TypeDB Workbase)

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

C
C++
Go
Java
Perl
Python
Ruby

All JVM based languages
Groovy
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

by using Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Multi-source replication

by using Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

by using Apache Kafka and Apache Zookeeper

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

substituted by the relationship feature

Transaction concepts

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

ACID

ACID at shard level

yes

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

at REST API level; other APIs in progress

More information provided by the system vendor

Specific characteristics

TypeDB is a polymorphic database with a conceptual data model, a strong subtyping...
» more

Competitive advantages

TypeDB provides a new level of expressivity, extensibility, interoperability, and...
» more

Typical application scenarios

Life sciences : TypeDB makes working with biological data much easier and accelerates...
» more

Licensing and pricing models

Apache f or language drivers, and AGPL and Commercial for the database server. The...
» more

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.