DBMS > Blazegraph vs. Couchbase vs. PlanetScale

System Properties Comparison Blazegraph vs. Couchbase vs. PlanetScale

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Primary database model

Graph DBMS
RDF store

Document store

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	0.74
Rank	#217	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Website

blazegraph.com

www.couchbase.com

planetscale.com

Technical documentation

wiki.blazegraph.com

docs.couchbase.com

planetscale.com/docs

Developer

Blazegraph

Couchbase, Inc.

PlanetScale

Initial release

2006

2011

2020

Current release

2.1.5, March 2019

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

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, C++, Go and Erlang

Server operating systems

Linux
OS X
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal types

yes

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
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

Server-side scripts

Stored procedures

yes

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

proprietary syntax

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Ephemeral buckets

yes

User concepts

Access control

Security and Authentication via Web Application Container (Tomcat, Jetty)

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Users with fine-grained authorization concept

no user groups or roles

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.