DBMS > BoltDB vs. OrigoDB vs. STSdb

System Properties Comparison BoltDB vs. OrigoDB vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A fully ACID in-memory object graph database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Document store
Object oriented DBMS

Key-value store

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

github.com/boltdb/bolt

origodb.com

github.com/STSSoft/STSdb4

Technical documentation

origodb.com/docs

Developer

Robert Friberg et al

STS Soft SC

Initial release

2013

2009

under the name LiveDB

2011

Current release

4.0.8, September 2015

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPLv2, commercial license available

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

primitive types and user defined types (classes)

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

.NET Client API
HTTP API
LINQ

.NET Client API

Supported programming languages

.Net

C#
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

depending on model

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

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

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.com

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

provided by Google News

Share this page