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

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

Editorial information provided by DB-Engines

Name

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

Widely used embeddable, in-process RDBMS

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Document store

Relational DBMS

Wide column store

Secondary database models

Graph DBMS
Search engine

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	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/boltdb/bolt

www.gigaspaces.com

cloud.google.com/datastore

www.sqlite.org

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

Technical documentation

docs.gigaspaces.com/latest/landing.html

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

Developer

Gigaspaces Technologies

Google

Dwayne Richard Hipp

Alex Kashirin

Initial release

2013

2000

2008

2000

2020

Current release

15.5, September 2020

3.45.3 (15 April 2024), April 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; Commercial licenses available

commercial

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.

Implementation language

Java, C++, .Net

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Solaris
Windows

hosted

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

SQL-like query language

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Proprietary protocol
Thrift

Supported programming languages

.Net
C++
Java
Python
Scala

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

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

yes

using Google App Engine

Triggers

yes, event driven architecture

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

via file-system locks

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

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

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.