DBMS > BoltDB vs. Google Cloud Datastore vs. SQLite vs. Stardog

System Properties Comparison BoltDB vs. Google Cloud Datastore vs. SQLite vs. Stardog

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used embeddable, in-process RDBMS

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

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	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

github.com/boltdb/bolt

cloud.google.com/datastore

www.sqlite.org

www.stardog.com

Technical documentation

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

docs.stardog.com

Developer

Google

Dwayne Richard Hipp

Stardog-Union

Initial release

2013

2008

2000

2010

Current release

3.45.3 (15 April 2024), April 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Public Domain

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

server-less

Linux
macOS
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

.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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

Callbacks using the Google Apps Engine

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

none

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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 in HA-Cluster

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

relationships in graphs

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

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

Access rights for users and 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.