Top all-time · #4623
Riak
Company blog · riak.com/postsdatasystems
Riak is the company blog at riak.com, writing about data and systems. Since 2019, 16 different Hacker News readers have linked it 16 times, most often “Bitcask: A Log-Structured Hash Table for Fast Key/Value Data [pdf]”. The last post was in 2016, but the archive is still widely read.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
HN readers link riak.com for Basho's technical writing: the Bitcask intro whitepaper, posts on vector clocks and CRDTs, and a critique of microservices. Riak's NHS deployment is also cited.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Riak provides NoSQL database solutions, enabling distributed systems to scale large amounts of unstructured data. Learn more about our NoSQL solutions!
Most-linked posts?
- Bitcask: A Log-Structured Hash Table for Fast Key/Value Data [pdf]4 people · 4 mentions · first linked 2019-04-10
- Microservices – Please, Don’t (2016)3 people · 3 mentions · first linked 2020-07-27
- /2 people · 2 mentions · first linked 2019-11-06
What Hacker News says?
Would Riak's Bitcask format fit the bill here? https://riak.com/assets/bitcask-intro.pdf
Comment linking /assets/bitcask-intro.pdf
on “Xg2xg: Lookup table of similar tech and services for ex-Googlers”Submitted Microservices – Please, Don’t (2016) as a story · 136 points
HN discussionNot papers or books, but I'd recommend you look at the blog articles and such that Basho published about their design of Riak. In particular, they wrote a great article explaining vector clocks as opposed to other synchronizing mechanisms, and they wrote several good articles on CRDTs. https://riak.com/category/technical/ - Riak blog https://www.allthingsdistributed.com/files/amazon-dynamo-sos... - Dynamo paper that…
Comment linking /category/technical/
on “Ask HN: Recommended books and papers on distributed systems?”Submitted Bitcask: A Log-Structured Hash Table for Fast Key/Value Data [pdf] as a story · 3 points
HN discussionAnd https://riak.com
Comment linking /
on “CRDT: Conflict-free replicated data type”Submitted Bitcask - A Log-Structured Hash Table for Fast Key/Value Data (2010) [pdf] as a story · 2 points
HN discussionIt'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...
Comment linking /posts/press/nhs-launches-upgraded-it-backbone-spine-powered-by-riak/index.html?p=5044.html
on “Open Riak – open, modern Riak fork”Submitted Why Vector Clocks are Easy (2010) as a story · 1 points
HN discussionI hadn't heard about bitcask before. Its design looks like a great alternative to LSM trees or B+trees like lmdb. Are there any good benchmarks comparing the approaches? The introductory whitepaper on bitcask's design is here: https://riak.com/assets/bitcask-intro.pdf
Comment linking /assets/bitcask-intro.pdf
on “Show HN: CaskDB – project to teach you building a key value store”Submitted Microservices – Please, Don’t (2016) as a story · 1 points
HN discussionMicroservices to reduce complexity and coupling is a fallacy. https://riak.com/posts/technical/microservices-please-dont/ is a great and succinct counter to all the advantages that microservices claim to have. In summary: > You don’t need to introduce a network boundary as an excuse to write better code > Distributed Transactions are never easy > A bunch of engineers working in isolated codebases leads to ‘Not my pr…
Comment linking /posts/technical/microservices-please-dont/
on “Drowning in code: The ever-growing problem of ever-growing codebases”Submitted Microservices – Please, Don’t (2016) as a story · 1 points
HN discussionI don't know of any rule of English grammar that would lead to this interpretation. If you do, you should immediately write to the maintainers of these websites: https://redis.com/nosql/key-value-databases/ https://www.mongodb.com/databases/key-value-database https://aws.amazon.com/nosql/key-value/ https://etcd.io/docs/v3.4/learning/why/ https://riak.com/products/riak-kv/ https://rocksdb.org/ https://github.com/goog…
Comment linking /products/riak-kv/
on “Warp: Lightweight Multi-Key Transactions for Key-Value Stores”Submitted Why Vector Clocks Are Hard (2010) as a story · 1 points
HN discussionInteresting website design: https://riak.com - reminds me of CSS Zen Garden. (Not that it says anything about how it performs etc.)
Comment linking /
on “Ask HN: Has anyone used Riak? Thoughts?”Apparently exists here: https://riak.com/why-vector-clocks-are-easy/index.html
Comment linking /why-vector-clocks-are-easy/index.html
on “Why Vector Clocks are Easy (2010)”
