DBMS > BoltDB vs. Hazelcast vs. PlanetScale vs. Snowflake vs. SWC-DB

System Properties Comparison BoltDB vs. Hazelcast vs. PlanetScale vs. Snowflake vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A widely adopted in-memory data grid

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

Cloud-based data warehousing service for structured and semi-structured data

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store

Relational DBMS

Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Time Series DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/boltdb/bolt

hazelcast.com

planetscale.com

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

hazelcast.org/imdg/docs

planetscale.com/docs

docs.snowflake.net/manuals/index.html

Developer

Hazelcast

PlanetScale

Snowflake Computing Inc.

Alex Kashirin

Initial release

2013

2008

2020

2014

2020

Current release

5.3.6, November 2023

0.5, April 2021

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL V3

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

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Docker
Linux
macOS

hosted

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

JavaScript (Node.js)
Python

C++

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

user defined functions

Triggers

yes

Events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

one or two-phase-commit; repeatable reads; read commited

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable 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.