←back to thread

219 points amarsahinovic | 1 comments | | HN request time: 0.418s | source
Show context
masleeds ◴[] No.42188652[source]
Riak has been maintained through the post-basho years by engineers at some of its larger customers (disclaimer - including myself).

The focus has been on trying to improve the stability of the database when subject to complex failure scenarios under stressful load, with minimal need for urgent operator intervention. The focus has been on keeping those existing operators happy rather than seeking out new users. Evolution of the product since basho has been slow but significant.

The project now has support from Erlang Ecosystem Foundation, and we're looking to invest some effort over the next few months explaining what we've done, and to start to articulate what we see as the future for Riak. So if you're interested watch this space.

It is expected to remain a niche product though. However, it may still find a home for those demanding specific non-functional requirements, with an acceptance of some functional constraints.

replies(2): >>42188991 #>>42189533 #
pton_xd ◴[] No.42189533[source]
> we're looking to invest some effort over the next few months explaining what we've done, and to start to articulate what we see as the future for Riak. So if you're interested watch this space.

Where's that going to be posted? I'm not a Riak user but I am interested in hearing what others are doing in regards to improving failure scenarios in distributed systems.

replies(1): >>42189607 #
1. masleeds ◴[] No.42189607[source]
When we get stuff together there will be a link from our discussions page - https://github.com/orgs/OpenRiak/discussions.
replies(2): >>42189801 #>>42189901 #