DBMS > BoltDB vs. Google Cloud Datastore vs. SingleStore vs. SQLite vs. SWC-DB

System Properties Comparison BoltDB vs. Google Cloud Datastore vs. SingleStore vs. SQLite vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Widely used embeddable, in-process RDBMS

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector 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	4.47
Rank	#76	Overall
	#12	Document stores

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/boltdb/bolt

cloud.google.com/datastore

www.singlestore.com

www.sqlite.org

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

Technical documentation

cloud.google.com/datastore/docs

docs.singlestore.com

www.sqlite.org/docs.html

Developer

Google

SingleStore Inc.

Dwayne Richard Hipp

Alex Kashirin

Initial release

2013

2008

2013

2000

2020

Current release

8.5, January 2024

3.45.3 (15 April 2024), April 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

MIT License

commercial

free developer edition available

Open Source

Public Domain

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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

C++, Go

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

64 bit version required

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (GQL)

yes

but no triggers and foreign keys

yes

SQL-92 is not fully supported

SQL-like query language

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Proprietary protocol
Thrift

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Bash
C
C#
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

hash partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» 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.