Riak

Last updated
Riak
Developer(s) Community Basho Technologies
Initial releaseAugust 17, 2009;14 years ago (2009-08-17)
Stable release
3.2.0 / January 1, 2023;8 months ago (2023-01-01) [1]
Repository
Written in Erlang
Operating system Linux, BSD, macOS, Solaris,Raspian
Platform IA-32, x86-64, AArch32
Type NoSQL Database, data store, Cloud storage
License Apache License 2.0
Website riak.com

Riak (pronounced "ree-ack" [2] ) is a distributed NoSQL key-value data store that offers high availability, fault tolerance, operational simplicity, and scalability. [3] Riak moved to an entirely open-source project in August 2017, with many of the licensed Enterprise Edition features being incorporated. [4] Riak implements the principles from Amazon's Dynamo paper [5] with heavy influence from the CAP theorem. Written in Erlang, Riak has fault-tolerant data replication and automatic data distribution across the cluster for performance and resilience. [6]

Contents

Riak has a pluggable backend for its core storage, with the default storage backend being Bitcask. [7] LevelDB is also supported, with other options (such as the pure-Erlang Leveled) available depending on the version.

Riak was originally developed by engineers employed by Basho Technologies [8] and maintained by them until 2017 when the rights were sold to bet365 [9] [10] after Basho went into receivership. [11]

Main features

Fault-tolerant availability
Riak replicates key/value stores across a cluster of nodes with a default n_val of three. In the case of node outages due to network partition or hardware failures, data can still be written to a neighboring node beyond the initial three, and read-back due to its "masterless" peer-to-peer architecture.
Queries
Riak provides a REST-ful API through HTTP and Protocol Buffers for basic PUT, GET, POST, and DELETE functions. More complex queries are also possible, including secondary indexes, search (via Apache Solr), and MapReduce. MapReduce has native support for both JavaScript (using the SpiderMonkey runtime) and Erlang.
Predictable latency
Riak distributes data across nodes with hashing and can provide latency profile, even in the case of multiple node failures.
Storage options
Keys/values can be stored in memory, disk, or both.
Multi-datacenter replication
Multi-Datacenter replication (MDC) provides uni-directional and bi-direction replication of data between Riak clusters, whether locally for resilience or globally for faster regional access. Uni-directional replication is useful for read-only sinks such as backups and Disaster Recovery sites. Bi-directional replication allows for multiple Riak cluster to have eventually consistent data across vast distances. Complex replication scenarios such as chains, hub-and-spoke and mesh networks are possible due to the Cascades feature, which allows replication of data between clusters that are not directly connected. There are two primary modes of operation: fullsync and realtime. Fullsync mode ensures that all data on the source cluster is replicated to the sink cluster. Only the metadata and changes are transferred, making this fast and efficient. Realtime mode sends updates made to a source cluster to the sink cluster in realtime. These modes are designed to work together for best performance All multi-datacenter replication occurs over multiple concurrent TCP connections to maximize performance and network utilization.
Tunable consistency
Option to choose between eventual and strong consistency for each bucket.

Main products

All versions of Riak are now entirely open-source and free, and include the extra features that Basho charged license fees for.

Basho operated a freemium model, wherein they provided free versions of Riak in the form of Riak Core, Riak KV, Riak CS and Riak TS but made their money from licensing more advanced features and SLA-based support. The extra features from the Enterprise Editions have since been integrated into the open source version of Riak KV, as of Riak KV release 2.2.6. [12] and Riak CS 2.1.2 [13]

Riak Core and Riak Core Lite

Riak Core

riak_core [14] is the distributed systems framework that underpins Riak, forming the foundation for all Riak versions. It is being maintained as part of Riak.

Riak Core Lite

riak_core_lite [15] is intended for general use as a base for creating distributed systems.

Riak KV (Key-Value)

Riak KV is a distributed NoSQL database designed to deliver maximum data availability by distributing data across multiple servers, meaning that if one client can reach one server, it should be able to read and write data. [16] KV went through a few names in its lifetime, starting as Riak then Riak DS (for Data Store) and finally Riak KV (for Key-Value).

When Basho Technologies went into receivership in 2017 [11] KV development was picked up by the open source community and has continued into 2021, with 2.2.6 released in 2018 being the first community release of KV. This release integrated some features that were originally restricted to Basho's Enterprise versions of Riak. [12]

Version 2.9.0 was the first major community release by the open source community, releasing in November 2019, [12] with version 3.0.1 following on August 20, 2020. [12] Development has continued since then with the latest release being version 3.0.7. [17]

Removed features

The current version of Riak no longer supports some features in the Enterprise edition of Riak, including:

  • SNMP/JMX support

Separated features in Riak KV 3.0+

The following features of Riak KV 2.x have been removed by default from the Riak build. Specific builds including these features are available.

  • Yokozuna

Riak CS (Cloud Storage)

Originally known as Riak Moss [18] (Riak Multi-tenant Object Storage System - MOSS) but named as Riak CS (Cloud Storage) when released, Riak CS was first publicly released in January 2012.

Riak CS (Cloud Storage) is object storage software built on top of Riak KV, Riak's distributed database. Riak CS is designed to provide simple, highly-available, distributed cloud storage at any scale, and can be used to build cloud architectures or as storage infrastructure for heavy-duty applications and services. [19]

Riak CS also includes an application called Stanchion [20] which is used to manage the serialization of requests. This enables Riak CS to manage globally unique entities like users and bucket names. Serialization in this context means that the entire cluster agrees upon a single value for any globally unique entity at any given time; when that value is changed, the new value must be recognized throughout the entire cluster.

Riak CS was briefly rebranded as Riak S2 to make it more obviously compatible with Amazon S3 but the name did not catch on and it reverted to Riak CS.

In 2021 development for Riak CS was resumed with contributions from TI Tokyo.

Riak TS (Time Series)

Riak TS is an extension to Riak KV optimized for time series data, in that:

A limited subset of SQL commands was implemented in Riak TS. There is no provision for consistency guarantees between tables (no foreign indexes). In SELECT statements, WHERE clause is supported but HAVING is not. ORDER BY was to appear in a version that was never released.

Riak TS existed as a collection of branches (in separate components of Riak KV such as riak_kv, riak_pb, etc.) and not as product with a repository of its own. It was developed by a dedicated team consisting of Gordon Guthrie (leader), Andy Till and Andrei Zavada, with occasional contributions from other developers.

Riak TS was conceived, along with Riak Data Platform project, as an attempt to diversify Basho's product line, an undertaking many insiders regard as misguided and eventually contributing to Basho's demise.

Licensing and support

Riak was originally licensed using a freemium model: open source versions of Riak KV, Riak CS and Riak TS are available, but end users can pay for additional features and support. However, since Basho entered receivership [11] and bet365 [10] (purchasers of all IP) made all Riak products fully open source, all the premium features are now available in the open source versions. Since Basho's demise, community [21] ad-hoc and paid support options have arisen.

Language support

Riak has official drivers for Ruby, Java, Erlang and Python. There are also numerous community-supported drivers for other programming languages. [22]

Community development

After bet365 [10] purchased the Riak IP, [9] the Riak products were made full open source and work to integrate premium features into the open source versions was completed with the 2.2.6 release.

History

Riak was originally written by Andy Gross and others at Basho Technologies [2] to power a web Sales Force Automation application by former engineers and executives from Akamai. There was more interest in the datastore technology than the applications built on it, so the company decided to build a business around Riak itself, gaining adoption throughout the Fortune 100 and becoming a foundation to many of the world's fastest-growing Web-based, mobile and social networking applications, as well as cloud service providers. Releases after graduation include

Riak KV

Riak 1.0 was released September 10, 2011

Riak KV Releases
Version!Date ReleasedChanges
1.0September 10, 2011Inition 1.0 Release [23]
1.1February 21, 2012Added Riaknostic, enhanced error logging and reporting, improved resiliency for large clusters, and a new graphical operations and monitoring interface called Riak Control.
1.4July 10, 2013Added counters, secondary indexing improvements, reduced object storage overhead, handoff progress reporting, and enhancements to MDC replication
2.0September 2, 2014Added new data types including sets, maps, registers, and flags simplifying application development. Strong consistency by bucket, full-text integration with Apache Solr, Security, and reduced replicas for Secondary sites.
2.1April 16, 2015Added an optimization for many write-heavy workloads – “write once” buckets – buckets whose entries are intended to be written exactly once, and never updated or over-written.
2.2November 17, 2016added Support for Debian 8 and Ubuntu 16.04, Solr integration improvements. [24]
2.2.6May 21, 2018The first community release. Added support for Multi-Datacentre Replication which was not part of open-source Riak before, added a grow-only set data type, improved data distribution over nodes and cleaned up production test issues. [25]
2.9.0November 20, 2019Added early support for TicTac Active Anti-Entropy, support for a new Riak specific backend called Leveled. [12]
2.9.1February 17, 2020Implements next-gen replication, [26] various changes to tombstones and bucket listing. [12]
2.9.7August 16, 2020Improved Active Anti-Entropy and improved Riak's overall stability.
2.9.8December 7, 2020Improved leveled functions [27]
2.9.9August 6, 2021Leveled stability improvements [28]
3.0.1August 20, 2020Adds support for OTP 20, 21, 22 but is not backwards compatible with previous OTP versions. [12]
3.0.2January 5, 2021Implements backend changes from 2.9.8, adds a range_check in the Tictac AAE based full-sync replication [12]
3.0.6May 8, 2021Adds location-awareness to cluster management, [29] along with bug fixes from 3.0.3 and 3.0.4. [12]
3.0.7July 21, 2021Reverts Riak erlang runtime system in interactive mode, rather than the embedded mode it was changed to previously. [17]
3.0.8October 12, 2021Support flushing of disk writes, implement read-repair for key ranges to accelerate recovery after known node outage [30]
3.0.9November 12, 2021Improve latency and expand statistics of secondary-index queries, including information about result counts and overall query time [31]
3.0.10March 30, 2022Improve memory management in leveled backend, add peer discovery without configuration changes, allow configuration of Erlang VM memory and scheduler settings via riak.conf [32]
3.0.11October 11, 2022Fix a bottleneck in secondary index queries with the leveled backend and > 1000 queries per second [33]
3.0.12December 20, 2022Improve memory management in the leveled backend, update leveldb snappy compression for wider platform support, introduce the reip_manual console command [34]
3.2.0January 1, 2023Support Erlang/OTP 22, 24, and 25, update to Erlang/OTP's new logging API, update packaging to include support for Alpine Linux and FreeBSD [35]
3.0.13February 4, 2023Improve reliability of handoffs, add administrative helper functions to riak_client [36]
3.0.14February 13, 2023Fix an issue related to handling back-pressure correctly in the leveled backend, add support for handing off reap requests via the handoff_deletes option [37]
3.0.15February 15, 2023Correct an issue introduced with the auto_check feature for TictacAAE full-sync introduced in 3.0.10 [38]

Riak CS

Riak CS was made open source on March 20, 2013 [39]

Riak CS Releases
Version!Date ReleasedChanges
0.0.3January 26, 2012The first public release of Riak CS. Known as Riak MOSS at the time. [40]
0.1.0February 25, 2012Bucket-level Access control, user record changes, Stanchion is now required. [41]
1.0.0April 2, 2012Fixes some process/socket leaks, adds a fix to prevent deadlock conditions, new subsystem for user access & storage usage calculations. [42]
1.0.1April 18, 2012Fixes a bug that caused requests to hang if a node in the cluster was unavailable [43]
1.1.0August 20, 2012Updates user creation, configuration options for anonymous users, more user account controls for admins, Garbage collection for deleted objects, improved performance. [44]
1.2.0October 23, 2012Early support for Multi-datacenter replication, support for riak_test integration, bug fixes. [45]
1.2.1January 23, 2016Add reduce phase for listing bucket contents to provide backpressure when executing the MapReduce job, Use prereduce during storage calculations, fixed incorrect 404 error when attempting to list contents of nonexistent bucket. [46]
1.2.2November 8, 2012Full support for MDC replication, fixed process leaks. [47]
1.3.0March 20, 2013Support for multi-part file uploads, bucket polices for restricted principles/conditions, range header. More administrative command controls, support for FreeBSD, SmartOS and Solaris Packaging. [48]
1.3.1April 4, 2013Bug fixes [49]
1.4.0August 12, 2013Early support for Swift API/Keystone Authentication, improved performance, bug fixes. [50]
1.5.0July 31, 2014Adds a multibag technical preview, new debug command, streamlines commands to new `riak-cs admin` command, improved garbage collection, updated lager, new API - Multiple objects, warning logs for manifests, siblings etc. [51]
1.5.1September 10, 2014Adds Bucket restrictions, adds sleep interval for manifest updates, updates riak-cs-debug, changes to bucket resolution. [52]
1.5.2October 9, 2014Improved logging for failures with Riak, Changes to log output for access stats, adds a script for invalid garbage collection manifest repairs. [53]
1.5.3December 12, 2014Add read_before_last_manifest_write option, Adds configurable timeouts for CS interactions with Riak [54]
1.5.4March 13, 2015Disable backpressure sleep, Fixes an incorrect path rewrite in S3 API [55]
2.0.0March 27, 2015Updates Riak CS to work with Riak 2.0.5, Changes gc_max_workers to gc.max_workers and changed default setting, early support for AWS v4 authentication, adds cuttlefish, storage optimisations. [56]
2.1.0October 14, 2015Final Basho release - Backwards compatible with KV 2.0.5, 21.1, Adds a large number of new metrics for health monitoring purposes along with storage usage metrics. Replaced commands with riak-cs-admin equivalents. Garbage collection improvements. [57]
2.1.1October 14, 2015Compatible with KV 2.1.3, 2.1.4, 2.2.x and 2.9.x
2.1.2April 9, 2019First post-basho release. [58]

Riak TS

Riak TS was originally released in October 2015 [59]

Riak TS Releases
Version!Date ReleasedChanges
1.2.0February 23, 2016Implements Riak_shell to allow SWQL commands & logging in a single shell in Riak TS. Bug fixes, Multi-Datacenter replication and riak search not supported. [60]
1.3.0May 4, 2016Open sources Riak TS, adds a HTTP API, additional SQL commands and support for MDC replication for enterprise users [61]
1.3.1July 5, 2016Addresses Data loss bug in 1.3.0. [62]
1.4.0August 24, 2016Adds new SQL features, Rolling upgrade/downgrade support, Global data expiry (per cluster). [63]
1.5.0December 20, 2016Expands SQL implementation, Improves data storage and improved overall performance. [64]
1.5.1January 24, 2017Bug fixes from 1.5.0 [65]
1.5.2February 21, 2017Bug Fixes from 1.5.1 [66]

Users

Notable users include AT&T, Comcast, [67] GitHub, [67] Best Buy, [67] UK National Health Services (NHS), [68] The Weather Channel, [69] and Riot Games. [70]

See also

Related Research Articles

<span class="mw-page-title-main">MySQL</span> SQL database engine software

MySQL is an open-source relational database management system (RDBMS). Its name is a combination of "My", the name of co-founder Michael Widenius's daughter My, and "SQL", the acronym for Structured Query Language. A relational database organizes data into one or more data tables in which data may be related to each other; these relations help structure the data. SQL is a language that programmers use to create, modify and extract data from the relational database, as well as control user access to the database. In addition to relational databases and SQL, an RDBMS like MySQL works with an operating system to implement a relational database in a computer's storage system, manages users, allows for network access and facilitates testing database integrity and creation of backups.

<span class="mw-page-title-main">PostgreSQL</span> Free and open-source relational database management system

PostgreSQL, also known as Postgres, is a free and open-source relational database management system (RDBMS) emphasizing extensibility and SQL compliance. It was originally named POSTGRES, referring to its origins as a successor to the Ingres database developed at the University of California, Berkeley. In 1996, the project was renamed to PostgreSQL to reflect its support for SQL. After a review in 2007, the development team decided to keep the name PostgreSQL and the alias Postgres.

The following tables compare general and technical information for a number of relational database management systems. Please see the individual products' articles for further information. Unless otherwise specified in footnotes, comparisons are based on the stable versions without any add-ons, extensions or external programs.

<span class="mw-page-title-main">Apache CouchDB</span> Document-oriented NoSQL database

Apache CouchDB is an open-source document-oriented NoSQL database, implemented in Erlang.

An embedded database system is a database management system (DBMS) which is tightly integrated with an application software; it is embedded in the application. It is a broad technology category that includes:

Spacewalk is open-source systems management software for system provisioning, patching and configuration licensed under the GNU GPLv2.

MongoDB is a source-available cross-platform document-oriented database program. Classified as a NoSQL database program, MongoDB uses JSON-like documents with optional schemas. MongoDB is developed by MongoDB Inc. and current versions are licensed under the Server Side Public License (SSPL) which is considered non-free by some organizations and distributions. MongoDB is a member of the MACH Alliance.

Moose File System (MooseFS) is an open-source, POSIX-compliant distributed file system developed by Core Technology. MooseFS aims to be fault-tolerant, highly available, highly performing, scalable general-purpose network distributed file system for data centers. Initially proprietary software, it was released to the public as open source on May 30, 2008.

<span class="mw-page-title-main">Redis</span> Open-source in-memory key–value database

Redis is an open-source in-memory storage, used as a distributed, in-memory key–value database, cache and message broker, with optional durability. Because it holds all data in memory and because of its design, Redis offers low-latency reads and writes, making it particularly suitable for use cases that require a cache. Redis is the most popular NoSQL database, and one of the most popular databases overall. Redis is used in companies like Twitter, Airbnb, Tinder, Yahoo, Adobe, Hulu, and Amazon.

LevelDB is an open-source on-disk key-value store written by Google fellows Jeffrey Dean and Sanjay Ghemawat. Inspired by Bigtable, LevelDB source code is hosted on GitHub under the New BSD License and has been ported to a variety of Unix-based systems, macOS, Windows, and Android.

<span class="mw-page-title-main">Basho Technologies</span>

Basho Technologies was a distributed systems' company that developed a key-value NoSQL database technology, Riak, and an object storage system built upon the Riak platform, called Riak CS.

FoundationDB is a free and open-source multi-model distributed NoSQL database developed by Apple Inc. with a shared-nothing architecture. The product was designed around a "core" database, with additional features supplied in "layers." The core database exposes an ordered key–value store with transactions. The transactions are able to read or write multiple keys stored on any machine in the cluster while fully supporting ACID properties. Transactions are used to implement a variety of data models via layers.

Druid is a column-oriented, open-source, distributed data store written in Java. Druid is designed to quickly ingest massive quantities of event data, and provide low-latency queries on top of the data. The name Druid comes from the shapeshifting Druid class in many role-playing games, to reflect that the architecture of the system can shift to solve different types of data problems.

Kubernetes is an open-source container orchestration system for automating software deployment, scaling, and management. Originally designed by Google, the project is now maintained by the Cloud Native Computing Foundation.

In distributed computing, a conflict-free replicated data type (CRDT) is a data structure that is replicated across multiple computers in a network, with the following features:

  1. The application can update any replica independently, concurrently and without coordinating with other replicas.
  2. An algorithm automatically resolves any inconsistencies that might occur.
  3. Although replicas may have different state at any particular point in time, they are guaranteed to eventually converge.

TiDB is an open-source NewSQL database that supports Hybrid Transactional and Analytical Processing (HTAP) workloads. It is MySQL compatible and can provide horizontal scalability, strong consistency, and high availability. It is developed and supported primarily by PingCAP and licensed under Apache 2.0. TiDB drew its initial design inspiration from Google's Spanner and F1 papers.

YDB (Yet another DataBase) is a distributed SQL database management system (DBMS) developed by Yandex, available as open-source technology.

References

  1. Riak 3.2.0 release notes, 2023-01-01
  2. 1 2 Sheehy, Justin. "Riak 1.0 Release Party". Vimeo.
  3. Harvey, Cynthia (23 May 2014). "60 Open Source Apps You Can Use in the Cloud". Datamation. Retrieved 5 June 2014.
  4. "Riak KV 2.2.6 Release Notes". github.com. April 26, 2018. Retrieved September 10, 2021.
  5. DeCandia, Giuseppe; Hastorun, Deniz; Jampani, Madan; Kakulapati, Gunavardhan; Lakshman, Avinash; Pilchin, Alex; Sivasubramanian, Swaminathan; Vosshall, Peter; Vogels, Werner (October 14–17, 2007). Dynamo: Amazon's Highly Available Key-value Store (PDF). Proceedings of 21st ACM SIGOPS Symposium on Operating Systems Principles (SOSP '07). Stevenson, Washington, USA: ACM. pp. 205–220. doi:10.1145/1294261.1294281. ISBN   978-1-59593-591-5 . Retrieved 5 June 2014.
  6. Morgan, Timothy Prickett (7 May 2014). "Eucalyptus Scales Out AWS Cloud Clone". Enterprise Tech. Retrieved 5 June 2014.
  7. "Basho: Bitcask". docs.riak.com. Retrieved 2021-09-14.
  8. "Basho Technologies", Wikipedia, 2020-11-19, retrieved 2021-07-15
  9. 1 2 "Riak NoSQL snapped up by Bet365". ComputerWeekly.com. Retrieved 2021-07-15.
  10. 1 2 3 "Bet365", Wikipedia, 2021-07-14, retrieved 2021-07-30
  11. 1 2 3 Hill, Rebecca. "End of the road for Basho: Court puts biz into receivership". www.theregister.com. Retrieved 2021-07-15.
  12. 1 2 3 4 5 6 7 8 9 "basho/riak". GitHub. Retrieved 2021-07-15.
  13. "basho/riak_cs". GitHub. Retrieved 2021-07-24.
  14. "Riak Core". GitHub .
  15. "Riak Core Lite". GitHub .
  16. "Riak KV". docs.Riak.com. 15 July 2021.
  17. 1 2 "Riak KV 3.0.7 Release notes". Riak Github. 2021-07-21. Retrieved 2021-09-02.
  18. "Riak Moss". Github. 2012-01-26. Retrieved 2021-08-24.
  19. "Riak Cloud Storage". docs.Riak.com. 15 July 2021.
  20. "Stanchion Application". Tiot.jp. Retrieved 2021-08-24.
  21. "Riak Community site". Riak info. 2021-09-14. Retrieved 2021-09-14.
  22. "Riak Client Libraries and Community Code" . Retrieved 5 June 2014.
  23. "Riak 1.0 release". Riak.com. 2011-09-11. Retrieved 2021-08-26.
  24. "Riak KV 2.2.0 Release Notes". Basho. 2016-11-17. Retrieved 2016-12-21.
  25. "Riak KV 2.2.5 Release Notes". GitHub . Retrieved 23 June 2018.
  26. "basho/riak_kv". GitHub. Retrieved 2021-07-15.
  27. "Riak KV 2.9.8 release notes". Github. 2020-12-07. Retrieved 2021-08-19.
  28. "Release notes 2.9.9". GitHub . 2021-08-06. Retrieved 2021-08-24.
  29. "basho/riak_core". GitHub. Retrieved 2021-07-15.
  30. "Riak KV 3.0.8 Release notes". Riak Github. 2021-10-12. Retrieved 2023-05-12.
  31. "Riak KV 3.0.9 Release notes". Riak Github. 2021-11-12. Retrieved 2023-05-12.
  32. "Riak KV 3.0.10 Release notes". Riak Github. 2022-03-30. Retrieved 2023-05-12.
  33. "Riak KV 3.0.11 Release notes". Riak Github. 2022-10-11. Retrieved 2023-05-12.
  34. "Riak KV 3.0.12 Release notes". Riak Github. 2022-12-20. Retrieved 2023-05-12.
  35. "Riak KV 3.2.0 Release notes". Riak Github. 2023-01-01. Retrieved 2023-05-12.
  36. "Riak KV 3.0.13 Release notes". Riak Github. 2023-02-04. Retrieved 2023-05-12.
  37. "Riak KV 3.0.14 Release notes". Riak Github. 2023-02-13. Retrieved 2023-05-12.
  38. "Riak KV 3.0.15 Release notes". Riak Github. 2023-02-15. Retrieved 2023-05-12.
  39. "Riak CS is now open source". Riak.com. 2013-03-20. Retrieved 2021-08-26.
  40. "Riak MOSS 0.0.3". Github. 2012-02-26. Retrieved 2021-09-02.
  41. "Riak CS 0.1.0 Release notes". Github. 2012-02-25. Retrieved 2021-09-02.
  42. "Moss 1.0 Release notes". Github. 2012-04-02. Retrieved 2021-09-02.
  43. "Moss 1.0.1 Release notes". Github. 2012-04-18. Retrieved 2021-09-02.
  44. "Riak CS 1.1.0 release notes". Riak CS Github. 2012-08-20. Retrieved 2021-09-02.
  45. "Riak CS 1.2 Release Notes". Riak CS Github. 2012-10-23. Retrieved 2021-09-02.
  46. "Riak CS 1.2.1 Release notes". Riak CS Github. 2012-10-23. Retrieved 2021-09-02.
  47. "Riak CS Release notes". Riak CS Github. 2012-11-08. Retrieved 2021-09-02.
  48. "Riak CS Release". Riak CS Github. 2013-03-20. Retrieved 2021-09-02.
  49. "Riak CS 1.3.1 Release notes". Riak CS Github. 2013-04-04. Retrieved 2021-09-02.
  50. "Riak CS 1.4.0 Release". Riak CS Github. 2013-08-12. Retrieved 2021-09-02.
  51. "Riak CS Release". Riak CS Github. 2014-07-31. Retrieved 2021-09-02.
  52. "Riak CS Release". Riak CS Github. 2014-09-10. Retrieved 2021-09-02.
  53. "Riak CS Releases". Riak CS github. 2014-10-09. Retrieved 2021-09-02.
  54. "Riak CS Release". Riak CS Github. 2014-12-12. Retrieved 2021-09-02.
  55. "Riak CS Releases". Riak CS Github. 2015-03-13. Retrieved 2021-09-02.
  56. "Docs.riak.com". Riak CS Release notes. 2015-03-27. Retrieved 2021-09-02.
  57. "Riak CS Release notes". Docs.riak.com. 2015-10-14. Retrieved 2021-09-02.
  58. "Riak CS github". Riak CS Github. 2019-04-09. Retrieved 2021-09-02.
  59. "Basho releases Riak TS (time-series)". InfoQ. 2015-10-27. Retrieved 2021-08-19.
  60. "Riak TS release notes". docs.riak.com. 2016-02-23. Retrieved 2021-09-14.
  61. "Riak TS 1.3.0 Release notes". docs.riak.com. 2016-05-04. Retrieved 2021-09-14.
  62. "Riak TS Release notes". docs.riak.com. 2016-07-05. Retrieved 2021-09-14.
  63. "Riak TS 1.4.0 Release notes". docs.riak.com. 2016-08-24. Retrieved 2021-09-14.
  64. "Riak TS 1.5.0 Release notes". docs.riak.com. 2016-12-20. Retrieved 2021-09-14.
  65. "Riak TS 1.5.1 Release notes". docs.riak.com. 2017-01-24. Retrieved 2021-09-02.
  66. "Riak TS 1.5.2 Release notes". docs.riak.com. 2017-02-21. Retrieved 2021-09-14.
  67. 1 2 3 "Basho Technologies takes aim at more enterprises with upgrades". 21 February 2013. Retrieved 26 March 2015.
  68. Clark, Jack (10 October 2013). "NHS tears out its Oracle Spine in favour of open source". The Register. Retrieved 5 June 2014.
  69. Henschen, Doug (2 June 2014). "Why Big Data Tools Are Here To Stay: InformationWeek Video". InformationWeek. Retrieved 5 June 2014.
  70. Ptaszek, Michal (16 January 2016). "Chat Service Architecture: Persistence". RiotGames. Retrieved 2 February 2016.