Live data from Hacker News

Open Riak – open, modern Riak fork

github.com

71–76 of 76 posts

Re: Open Riak – open, modern Riak fork

#71
post #32

As someone who has used Riak in anger once in his career and who has a blossoming interest in FoundationDB I'd love someone to contrast the two systems. My knee-jerk reaction --- which I'm calling out as such! --- is that FDB has decreased the relevance of systems like Riak.

I spent a lot of time with NoSQL systems in the early 2010s and I think what “killed” them was processors and networks getting so much faster that Postgres “just worked” for more and more use cases.

There are systems I’ve built in the past with 20+ Cassandra nodes and tens of thousands of ops that were originally built on MySQL/Postgresql but migrated to Cassandra because the performance/cost of the SQL systems was just to high.

Now those performance requirements can be handled cheaply with 1 or 2 beefy PostgreSQL databases. The level of scale you need today to make put up with something like Cassandra is much higher while yesteryear it felt like every startup was falling over once they found pmf

Re: Open Riak – open, modern Riak fork

#72
post #5

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.

I think that in the time since 2011, things have changed more than a bit. As my employer provides Enterprise Grade Riak Support (and, of course, OpenRiak support), I'm under NDA and cannot really share names. However, I can share that that there are quite a few places that use Riak. Here are a few off the top of my head: - the biggest online betting company in the world - one of Japan's largest e-commerce sites - a l…

Crypto taxes? You do automated crypto trading?

Re: Open Riak – open, modern Riak fork

#73
post #53
post #49

Earlier quoted context omitted.

What does metastability mean in this context? I've only seen it used to mean "appears stable but not actually stable", eg systems that resist small perturbations but never return to nominal after bigger disturbance (like cold boot). Did you mean "stability"?

Marc Brooker’s blog on the topic is good: https://brooker.co.za/blog/2021/05/24/metastable.html

That's exactly what I mean, that's why I'm asking what GP meant.

Re: Open Riak – open, modern Riak fork

#74
post #7

I've never met an engineering team that used Riak, but it is used heavily as an example technology in Kleppmann's 'Designing Data Intensive Applications'. (I would say, informally, it's usually the example of the "other way" as opposed to other more well-known databases.) This does make me wonder what became of it, why it didn't take off.

> I've never met an engineering team that used Riak I was part of a recent cloud migration. Part of on-prem (though unfortunately not migrated by my team) were this very first Riak Cluster I saw in production. The engineering team used it as "kind of S3" for images, with 3 to 5 PHP scripts providing an interface to Riak and imageMagic. It seemed to me like a good abstraction and I think the migration to S3 was mostly…

I've talked to some people who use Riak as an S3 and reported that their reasoning for sticking to it is 2 to 4 orders of magnitude faster than S3. This blew my mind, but then they showed me 20ms response times from their Riak cluster and 2-second response times from S3. Now, I think these aren't standard, and in my experience, I'd say Riak is more like a single order of magnitude faster.

Re: Open Riak – open, modern Riak fork

#76
post #74

Earlier quoted context omitted.

> I've never met an engineering team that used Riak I was part of a recent cloud migration. Part of on-prem (though unfortunately not migrated by my team) were this very first Riak Cluster I saw in production. The engineering team used it as "kind of S3" for images, with 3 to 5 PHP scripts providing an interface to Riak and imageMagic. It seemed to me like a good abstraction and I think the migration to S3 was mostly…

I've talked to some people who use Riak as an S3 and reported that their reasoning for sticking to it is 2 to 4 orders of magnitude faster than S3. This blew my mind, but then they showed me 20ms response times from their Riak cluster and 2-second response times from S3. Now, I think these aren't standard, and in my experience, I'd say Riak is more like a single order of magnitude faster.

I would imagine that most of that is probably due to latency. Which might already be worth the extra effort, depending on the usecase.
Post reply on HN