(github.com)

219 points amarsahinovic | 1 comments | 19 Nov 24 20:29 UTC | HN request time: 0.349s | source

Show context

vosper ◴[19 Nov 24 21:03 UTC] No.42188052[source]▶

Who would this be for in 2024?

I remember evaluating Riak back in 2011 or so for an analytics solution, but ended up going with a more traditional OLAP database that was a much better option.

It's hard for me to imagine where Riak would be a good option given how many choices we have today for various data stores.

replies(4): >>42188103 #>>42188656 #>>42188698 #>>42190677 #

1. EwanToo ◴[19 Nov 24 22:17 UTC] No.42188698[source]▶

>>42188052 #

It's realistically for the handful (dozens at most?) of very large Riak implementations where it would be enormously expensive to rewrite the application running on top of it.

For example, the UK NHS Spine messaging system which has been building on Riak for 10 years

https://riak.com/posts/press/nhs-launches-upgraded-it-backbo...

↑

Open Riak – open, modern Riak fork