DBMS > BoltDB vs. SAP HANA

System Properties Comparison BoltDB vs. SAP HANA

Please select another system to include it in the comparison.

Our visitors often compare BoltDB and SAP HANA with Redis, MongoDB and Elasticsearch.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.99
Rank	#230	Overall
	#35	Key-value stores

Score	51.42
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/boltdb/bolt

www.sap.com/products/hana.html

Technical documentation

help.sap.com/hana

Developer

SAP

Initial release

2013

2010

Current release

2.0 SPS06 (March 4, 2022), March 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC
ODBC

Supported programming languages

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

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

yes

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.