DBMS > BoltDB vs. CouchDB vs. Spark SQL vs. SQLite vs. TigerGraph

System Properties Comparison BoltDB vs. CouchDB vs. Spark SQL vs. SQLite vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

github.com/boltdb/bolt

Technical documentation

docs.couchdb.org/en/stable

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

docs.tigergraph.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2013

2005

2014

2000

2017

Current release

3.3.3, December 2023

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

Public Domain

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Scala

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java
Python
R
Scala

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++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

yes

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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 can be defined per database

Role-based access control

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.