🦞🌯 Lobster Roll

How we at GO-JEK built resiliency in Distributed systems at scale

I am collating ideas on bringing resiliency in distributed systems at scale. I had previously written a article on this here: https://blog.gojekengineering.com/resiliency-in-distributed-systems-efd30f74baf4 Above article includes: 1) Timeouts 2) Retries 3) Circuit breakers 4) Fallbacks 5) R...

This is part 2 of my thoughts building resilience in large scale distributed systems

After a year of writing, my book Distributed Systems with Node.js was finally published today! The book is available here: * [Paperback from O'Reilly](https://shop.aer.io/oreilly/p/distributed-systems-with/9781492077299-9149) (use coupon code DSWN20 for 20% off!) * [Paperback/Kindle from Amazon]...

Seems relevant to some of the crowd I know is here. I would have used it on e.g. https://lobste.rs/s/clzzho/edelweiss_automatic_storage_reclamation_for_distributed_programming

I had wondered about this in the past - how to actually teach people about distributed systems architecture when you don't have the opportunity to work on a system that generates a ton of traffic. I am interested to see how they will structure the challenges. I assume they are not going to be sen...

See also https://news.ycombinator.com/item?id=4164991.

In light of http://blog.empathybox.com/post/90318905473/concurrency-is-not-a-language-thing-anymore and http://arschles.github.io/2014/06/25/concurrency-mem-mgmt.html both recently making it onto lobste.rs recently, I think that bloom might be of interest to those who haven't heard of it before.