Questionable deletion

edit

What was the reason for this deletion? [1]. It was deleted with no comment, and it's properly cited. Deletion has been reverted; please discuss here before deleting it again. This article reads too much like an ad, and needs to be more balanced. Thanks. --John Nagle (talk) 06:59, 19 January 2014 (UTC)Reply


I would say the deletion is because that issue isn't necessarily specific to Riak. I've read that case study, and what it boils down to in my view is that the implementers did not understand the implications of heavily using MapReduce in large clusters, and therefore shot themselves in the foot. They then switched to traditional RDB technology which they should have been using in the first place. 2601:681:4D04:6560:B8DD:5CC6:912:D2DE (talk) 23:37, 18 August 2015 (UTC)Reply

Takeover by Bet365

edit

Looks like Riak has a new owner - http://www.computerweekly.com/news/450426130/Riak-NoSQL-snapped-up-by-bet365 Qrilka (talk) 07:54, 6 November 2017 (UTC)Reply

Update for 2020-03

edit

This article is very out-of-date. Any objections to updating this to reflect the current situation?

Was thinking of adding:

  • give a breakdown of the projects under Riak - specifically Riak Core, Riak KV, Riak CS (and Stanchion) and Riak TS. (src: riak.com)
  • update features to include new 2.9.x features such as a pure erlang backend in leveled. (src: Github)
  • updating project history to include Basho's demise, purchase by Bet365 and subsequent release as open-source (src: news websites, press releases).
  • updating development history to detail major changes in 2.2.6, 2.9.0p5, and 2.9.1. (src: Github release notes); removing 2.2.5 as that was never actually a release due to a tagging issue on Github.
  • adding a current development section to cover the v3.0.0 uplift from OTP r16b02_basho10 to OTP 20 that is currently nearing completion (src: mailing lists).
  • adding future plans section to cover uplifting to OTP22 (src: mailing lists). — Preceding unsigned comment added by PeterJAClark (talkcontribs) 00:50, 10 March 2020 (UTC)Reply

Category

edit

Will anybody object if I add "Category:Free database management systems" to the list of categories (at the bottom)? 185.3.33.31 (talk) 17:11, 20 April 2021 (UTC)AnonymReply

Sounds very sensible to me. PeterJAClark (talk) 12:51, 9 September 2021 (UTC)Reply

Draft:Riak

edit

This draft was created from a copy of this article. It is preferable to improve this article directly. If there is a WP:COI issue you can propose changes and have them reviewed by neutral edirots. I have redirected the draft here. The improvements made to the draft are still available in its history. ~Kvng (talk) 15:01, 8 September 2021 (UTC)Reply

Large update to Riak covering last 4 years

edit
  • What I think should be changed: User:PeterJAClark/Draft_of_large_update_to_Riak
  • Why it should be changed: This article hasn't been updated properly since Basho (the company behind Riak) went bankrupt in 2017. Since then an incredible amount has changed, resulting in changes to nearly every section. The IP was bought by a company (not mine), who made it all open source, my company started providing commercial support for Riak to ex-Basho customers, and a community developed to continue development. New features have been added, previously paid-only features have been made open-source, some features have been dropped. Not sure there's a single section that hasn't needed updates.
  • References supporting the possible change (format using the "cite" button): Citations are given in the proposed changes at User:PeterJAClark/Draft_of_large_update_to_Riak


PeterJAClark (talk) 09:21, 17 September 2021 (UTC)Reply

References

PeterJAClark, I see your heavy work, but I need to close the request at this time without any action. As main features and main product section contain unreferenced information. Please see Verifiability and Reliable Sources. Again, you are required to raise another edit request. Before that please take some time to understand the guideline on how to make a proper edit request so that it is responded promptly, where you will learn how to detail where you want to change, what you want to change. Preferably you need to mention the edits you want to make within the edit request itself, not at some other place. You can your user sandbox if you need some place to do rough works. Chirota (talk) 05:42, 22 September 2021 (UTC)Reply

Update for the first paragraph, to include details of Riaks maintenance post-Basho, including the open sourcing and intergration of enterprise features.

edit
  • What I think should be changed: The main "Riak" section to include changes since Basho went bankrupt, including the integration of Enterprise features into the newly open sourced version. Example version below. Specifically,
  • Why it should be changed: Though the article mentions that Riak is open source, the opening section refers to Riak as being available in supported enterprise versions, which is no longer accurate (since basho has gone bankrupt and the features were integrated into Riak itself)
  • References supporting the possible change (format using the "cite" button): Citations are included in the suggested edit below

Riak (pronounced "ree-ack") is a distributed NoSQL Key-value data store that offers high availability, fault tolerance, operational simplicity, and scalability. Riak moved to an entirely open-source project in August 2017, with many of the licensed Enterprise Edition features being incorporated. Riak implements the principles from Amazon's Dynamo paper 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.

Riak has a pluggable backend for its core storage, with the default storage backend being Bitcask LevelDB is also supported, with other options (such as the pure-Erlang Leveled[1]) 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[2][3] after Basho went into receivership[4].

JosephPearl (talk) 14:21, 13 October 2021 (UTC) :  Not done: The proposed changes are already covered elsewhere in the article. Quetstar (talk) 22:52, 30 October 2021 (UTC)Reply

  Partly done: Thank you. I made changes based on your suggestions, with some appropriate tweaks due to sourcing. PK650 (talk) 23:15, 24 November 2021 (UTC)Reply
  • What I think should be changed: Updates to the main page to include a section on community development and update to the history section to include the 3.0.1 milestone
  • Why it should be changed: Community developers are the main source of updates for Riak post-basho, with developers from different companies and communities contributing to it's releases, and 3.0 specifically doesn't exist, with 3.0.1 being the first major 3.x release.
  • References supporting the possible change: [5] [6]

Example section for community development:

Community development

After bet365 purchased the Riak IP , 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.

JosephPearl (talk) 13:24, 13 January 2022 (UTC)Reply

  1. ^ "Leveled Github". Github. Martin Sumner. Retrieved 2021-10-13.
  2. ^ "Riak NoSQL snapped up by Bet365". Computer Weekly. Computer Weekly. Retrieved 2021-10-13.
  3. ^ "Bet 365". Wikipedia. Retrieved 2021-10-13.
  4. ^ "End of the road for Basho". The Register. The Register. Retrieved 2021-10-13.
  5. ^ Gtihub https://github.com/basho/riak/blob/develop-3.0/RELEASE-NOTES.md#riak-kv-301-release-notes. Retrieved 13 January 2022. {{cite web}}: Missing or empty |title= (help)
  6. ^ Tiot https://www.tiot.jp/riak-docs/riak/kv/2.2.6/release-notes/. Retrieved 13 January 2022. {{cite web}}: Missing or empty |title= (help)