/Architecture

Growth Engineering at Netflix - Accelerating Innovation

tl;dr: Insight into the signup architecture at Netflix. An overview of the UX on mobile / TV and how the stack is configured to support this flow. If you're paywalled, click the link in this tweet.

featured in #147


Design Systems And Front-End Architecture

- Stuart Robson tl;dr: What is a design system, why it's used and how to go about building one along with examples. Also, an in-depth guide as to how to construct a system.

featured in #147


Bringing Service Workers To Google Search

- Jeff Posnick tl;dr: Google Search Results, under certain circumstances, are served by a piece of technology called a service worker. This article runs through their implementation, how performance was measured and tradeoffs. Interesting insight into operations at Google.

featured in #146


Proving Security At Scale With Automated Reasoning

- Werner Vogels tl;dr: Fascinating run-through of how AWS thinks about security at scale, starting with the Shared Responsibility Model where AWS is responsible for security of the cloud and customers are responsible for security in the cloud.

featured in #146


Python at Netflix

tl;dr: High-level run through of how Python is used in the content life-cycle at Netflix along with mentions of the open-source packages used.

featured in #139


How Data Layout Affects Memory Performance

- William Cohen tl;dr: Developers can improve performance of memory intensive applications by designing data structures to mirror the way in which modern memory is stored by (1) arranging layout to minimize reading/writing useless bytes (2) minimize random accesses (3) access elements with predictable stride.

featured in #135


Architecting UIs For Change

- Henrik Joreteg tl;dr: As complex web apps increase in scope, architectural integrity is sacrificed due to the oversight of how data will interact within the app later on. This article guides us on how to structure a Redux app that scales as data needs to interact in initially unexpected ways.

featured in #134


Give Me Back My Monolith

- Craig Kerstiens tl;dr: Much has been made about micro-services, but downsides include more time onboarding new devs & increased complexity debugging.

featured in #133


Refactoring Python Applications for Simplicity

- Anthony Shaw tl;dr: In its own words, this tutorial walks through: How to measure complexity of your code & app How to change your code without breaking it Common issues in Python that add complexity & how to fix them

featured in #132


How Is Software Developed At Amazon?

- Todd Hoff tl;dr: Fireside chat with Ken Exner, GM at AWS Dev Tools. The article summarizes it more extensively than I will. Key ideas are: Create more autonomy and higher velocity by moving away from monolithic architecture towards microservices and two pizza teams 🍕🍕 Automate everything Culture of ownership and accountability. Two pizza teams own everything relevant to their product. They acts like startups, managers oversee startups Are the short summaries (tl;dr sections) helpful? Please vote here

featured in #131