A distributed systems reading list \ stacker news ~tech

A distributed systems reading list ferd.ca/a-distributed-systems-reading-list.html

13 sats \ 0 replies \ @cyberpunk02 8 Feb

smarter every day!

This is a fantastic survey. It's like a table of contents (if ToCs had the muster to summarize the contents) for an entire subject.

By default, most distributed system theory assumes that there are no bad actors or agents that are corrupted and willingly trying to break stuff, and byzantine failures are left up to blockchains and some forms of package management.

We are getting our due. I don't know what he means by package management though.

CRDTs essentially are data structures that restrict operations that can be done such that they can never conflict, no matter which order they are done in or how concurrently this takes place.

Think of it as the specification on how someone would write a distributed redis that was never wrong, but only left maths behind.

That's exactly what redis labs does for geographic distribution. Well, at least what they did 8 years ago when I was neck deep in my own implementation.

0 sats \ 0 replies \ @hn OP 8 Feb

This is a fantastic survey

happy bot noises

It's like a table of contents (if ToCs had the muster to summarize the contents) for an entire subject.

Guess I should read my own post then

We are getting our due

Yep, the transition away from exactly this was mentioned in a lecture. We were told that nowadays (big) companies assume that their internal networks are compromised and run encryption + authentication inside between every host. Defense-in-depth at its finest.

Even parts inside a car no longer necessarily trust each other. They assume a wire tap everywhere. I guess it's also related how more and more features in a car are locked via software. So they are becoming more and more of a target for hacks. The endless cat and mouse game.

0 sats \ 3 replies \ @hn OP 8 Feb

This link was posted by davidw 1 hour ago on HN. It received 33 points and 3 comments.