Developer(s) | Community Basho Technologies |
---|---|
Initial release | August 17, 2009 |
Stable release | 3.2.0 / January 1, 2023 [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 |
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]
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]
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 [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 [15] is intended for general use as a base for creating distributed systems.
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]
The current version of Riak no longer supports some features in the Enterprise edition of Riak, including:
The following features of Riak KV 2.x have been removed by default from the Riak build. Specific builds including these features are available.
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 is an extension to Riak KV optimized for time series data, in that:
CREATE TABLE
call) required before data can be written;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.
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.
Riak has official drivers for Ruby, Java, Erlang and Python. There are also numerous community-supported drivers for other programming languages. [22]
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.
Riak was originally written by Andy Gross and Justin Sheehy 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 1.0 was released September 10, 2011
Version! | Date Released | Changes |
---|---|---|
1.0 | September 10, 2011 | Inition 1.0 Release [23] |
1.1 | February 21, 2012 | Added Riaknostic, enhanced error logging and reporting, improved resiliency for large clusters, and a new graphical operations and monitoring interface called Riak Control. |
1.4 | July 10, 2013 | Added counters, secondary indexing improvements, reduced object storage overhead, handoff progress reporting, and enhancements to MDC replication |
2.0 | September 2, 2014 | Added 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.1 | April 16, 2015 | Added 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.2 | November 17, 2016 | added Support for Debian 8 and Ubuntu 16.04, Solr integration improvements. [24] |
2.2.6 | May 21, 2018 | The 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.0 | November 20, 2019 | Added early support for TicTac Active Anti-Entropy, support for a new Riak specific backend called Leveled. [12] |
2.9.1 | February 17, 2020 | Implements next-gen replication, [26] various changes to tombstones and bucket listing. [12] |
2.9.7 | August 16, 2020 | Improved Active Anti-Entropy and improved Riak's overall stability. |
2.9.8 | December 7, 2020 | Improved leveled functions [27] |
2.9.9 | August 6, 2021 | Leveled stability improvements [28] |
3.0.1 | August 20, 2020 | Adds support for OTP 20, 21, 22 but is not backwards compatible with previous OTP versions. [12] |
3.0.2 | January 5, 2021 | Implements backend changes from 2.9.8, adds a range_check in the Tictac AAE based full-sync replication [12] |
3.0.6 | May 8, 2021 | Adds location-awareness to cluster management, [29] along with bug fixes from 3.0.3 and 3.0.4. [12] |
3.0.7 | July 21, 2021 | Reverts Riak erlang runtime system in interactive mode, rather than the embedded mode it was changed to previously. [17] |
3.0.8 | October 12, 2021 | Support flushing of disk writes, implement read-repair for key ranges to accelerate recovery after known node outage [30] |
3.0.9 | November 12, 2021 | Improve latency and expand statistics of secondary-index queries, including information about result counts and overall query time [31] |
3.0.10 | March 30, 2022 | Improve 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.11 | October 11, 2022 | Fix a bottleneck in secondary index queries with the leveled backend and > 1000 queries per second [33] |
3.0.12 | December 20, 2022 | Improve memory management in the leveled backend, update leveldb snappy compression for wider platform support, introduce the reip_manual console command [34] |
3.2.0 | January 1, 2023 | Support 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.13 | February 4, 2023 | Improve reliability of handoffs, add administrative helper functions to riak_client [36] |
3.0.14 | February 13, 2023 | Fix 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.15 | February 15, 2023 | Correct an issue introduced with the auto_check feature for TictacAAE full-sync introduced in 3.0.10 [38] |
Riak CS was made open source on March 20, 2013 [39]
Version! | Date Released | Changes |
---|---|---|
0.0.3 | January 26, 2012 | The first public release of Riak CS. Known as Riak MOSS at the time. [40] |
0.1.0 | February 25, 2012 | Bucket-level Access control, user record changes, Stanchion is now required. [41] |
1.0.0 | April 2, 2012 | Fixes some process/socket leaks, adds a fix to prevent deadlock conditions, new subsystem for user access & storage usage calculations. [42] |
1.0.1 | April 18, 2012 | Fixes a bug that caused requests to hang if a node in the cluster was unavailable [43] |
1.1.0 | August 20, 2012 | Updates user creation, configuration options for anonymous users, more user account controls for admins, Garbage collection for deleted objects, improved performance. [44] |
1.2.0 | October 23, 2012 | Early support for Multi-datacenter replication, support for riak_test integration, bug fixes. [45] |
1.2.1 | January 23, 2016 | Add 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.2 | November 8, 2012 | Full support for MDC replication, fixed process leaks. [47] |
1.3.0 | March 20, 2013 | Support 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.1 | April 4, 2013 | Bug fixes [49] |
1.4.0 | August 12, 2013 | Early support for Swift API/Keystone Authentication, improved performance, bug fixes. [50] |
1.5.0 | July 31, 2014 | Adds 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.1 | September 10, 2014 | Adds Bucket restrictions, adds sleep interval for manifest updates, updates riak-cs-debug, changes to bucket resolution. [52] |
1.5.2 | October 9, 2014 | Improved logging for failures with Riak, Changes to log output for access stats, adds a script for invalid garbage collection manifest repairs. [53] |
1.5.3 | December 12, 2014 | Add read_before_last_manifest_write option, Adds configurable timeouts for CS interactions with Riak [54] |
1.5.4 | March 13, 2015 | Disable backpressure sleep, Fixes an incorrect path rewrite in S3 API [55] |
2.0.0 | March 27, 2015 | Updates 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.0 | October 14, 2015 | Final 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.1 | October 14, 2015 | Compatible with KV 2.1.3, 2.1.4, 2.2.x and 2.9.x |
2.1.2 | April 9, 2019 | First post-basho release. [58] |
Riak TS was originally released in October 2015 [59]
Version! | Date Released | Changes |
---|---|---|
1.2.0 | February 23, 2016 | Implements 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.0 | May 4, 2016 | Open sources Riak TS, adds a HTTP API, additional SQL commands and support for MDC replication for enterprise users [61] |
1.3.1 | July 5, 2016 | Addresses Data loss bug in 1.3.0. [62] |
1.4.0 | August 24, 2016 | Adds new SQL features, Rolling upgrade/downgrade support, Global data expiry (per cluster). [63] |
1.5.0 | December 20, 2016 | Expands SQL implementation, Improves data storage and improved overall performance. [64] |
1.5.1 | January 24, 2017 | Bug fixes from 1.5.0 [65] |
1.5.2 | February 21, 2017 | Bug Fixes from 1.5.1 [66] |
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]
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.
PostgreSQL, also known as Postgres, is a free and open-source relational database management system (RDBMS) emphasizing extensibility and SQL compliance. PostgreSQL features transactions with atomicity, consistency, isolation, durability (ACID) properties, automatically updatable views, materialized views, triggers, foreign keys, and stored procedures. It is supported on all major operating systems, including Linux, FreeBSD, OpenBSD, macOS, and Windows, and handles a range of workloads from single machines to data warehouses or web services with many concurrent users.
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.
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 product, MongoDB utilizes JSON-like documents with optional schemas. MongoDB is developed by MongoDB Inc. and current versions are licensed under the Server Side Public License (SSPL). 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.
Redis is a source-available, 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, Amazon and OpenAI.
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.
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.
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:
RocksDB is a high performance embedded database for key-value data. It is a fork of Google's LevelDB optimized to exploit multi-core processors (CPUs), and make efficient use of fast storage, such as solid-state drives (SSD), for input/output (I/O) bound workloads. It is based on a log-structured merge-tree data structure. It is written in C++ and provides official language bindings for C++, C, and Java. Many third-party language bindings exist. RocksDB is free and open-source software, released originally under a BSD 3-clause license. However, in July 2017 the project was migrated to a dual license of both Apache 2.0 and GPLv2 license. This change helped its adoption in Apache Software Foundation's projects after blacklist of the previous BSD+Patents license clause.
Enonic XP is a free and open-source web application platform and content management system (CMS) in one based on Java and Elasticsearch. Developed by the Norwegian software company Enonic, the microservice web platform can be used to build progressive web applications, Next.js websites, or web-based APIs. Enonic XP uses an application framework for coding server logic with JavaScript, and has no need for SQL as it ships with an integrated content repository. The CMS is fully decoupled, meaning developers can create traditional websites and landing pages, or use XP in headless mode, that is without the presentation layer, for loading editorial content onto any device or client. Enonic is used by major organizations in Norway, including the national postal service Norway Post, the insurance company Gjensidige, the national lottery Norsk Tipping, the Norwegian Labour and Welfare Administration, and all the top football clubs in the national football league for men, Eliteserien.
TiDB is an open-source NewSQL database that supports Hybrid Transactional and Analytical Processing (HTAP) workloads. Designed to be MySQL compatible, it is developed and supported primarily by PingCAP and licensed under Apache 2.0. It is also available as a paid product. TiDB drew its initial design inspiration from Google's Spanner and F1 papers.
RavenDB is an open-source document-oriented database written in C#, developed by Hibernating Rhinos Ltd. It is cross-platform, supported on Windows, Linux, and Mac OS. RavenDB stores data as JSON documents and can be deployed in distributed clusters with master-master replication.
Valkey 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, Valkey offers low-latency reads and writes, making it particularly suitable for use cases that require a cache. Valkey is the successor to Redis, the most popular NoSQL database, and one of the most popular databases overall. Valkey or its predecessor Redis are used in companies like Twitter, Airbnb, Tinder, Yahoo, Adobe, Hulu, Amazon and OpenAI.