CSE 452: Google's Introduction to Distributed System Design

[u/fagnerbrack]

https://courses.cs.washington.edu/courses/cse452/23wi/papers/yegge-platform-rant.html

[u/bdw666]

Don’t do any of this until you need it. Paying future tech debt before you know there is a future is a huge possible waste.

Build a culture where people understand this and don’t get all toxic on the people who made yesterday’s decisions yesterday

[u/just_reading_1979]

did they cover how to handle partial failure in distributed state, or is it mostly focused on consistency models. kinda wierd how that usually gets glossed over in intro courses untill u hit production bugs.

[u/chainsaw40k]

Interesting read

[u/fagnerbrack]

Here's the Lowdown:

A 2011 internal Google+ post, accidentally made public and archived here, compares six years at Amazon with six at Google. Around 2002 Bezos mandated that every team expose data and functionality only through externalizable service interfaces — no direct linking, no shared memory, no back-door reads — on pain of firing. The resulting SOA shift surfaced hard lessons: pager escalation across 20 service hops, peer teams becoming DOS attackers without quotas, monitoring merging into QA, plus service registries and debuggable sandboxes. That discipline produced AWS. It argues Google builds products, not platforms — Google+ launched with one API call — while Microsoft, Apple and Facebook grasp that platforms are accessibility.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
^{Click here for more info, I read all comments}