/Architecture

Uber’s Unified Signup and Login Stack

tl;dr: "Over the years we’ve built independent signup and login experiences for each of our lines of business which allowed us to innovate and move a lot quicker. However, as we scaled and added additional lines of business, our experiences began to diverge leading to some of these inconsistencies being amplified."

featured in #323

Airbnb’s Microservices Architecture Journey To Quality Engineering

- Antoine Craske tl;dr: Airbnb went through this process implementing the following practices: (1) Provide infrastructure as code to improve developer’s productivity. (2) Clarify ownership and improve with tooling & observability. (3) Define a new architecture supported by organization & methods. (4) Lead a deprecation working group to accelerate the migration. Antoine discusses how each was solved.

featured in #317

Emerging Architectures For Modern Data Infrastructure

- Matt Bornstein Jennifer Li Martin Casado tl;dr: "To help data teams stay on top of the changes happening in the industry, we’re publishing in this post an updated set of data infrastructure architectures. They show the current best-in-class stack across both analytic and operational systems, as gathered from numerous operators we spoke with over the last year."

featured in #304

On Building Scalable Systems

- Kislay Verma tl;dr: "Scalability is the idea that a system should be able to handle an increase in workload by employing more computing resources without significant changes to its design." The key axes of scalability are latency, throughput & capacity. Kislay discusses each, as well as how to quantify scalability, and more.

featured in #303

Rapid Event Notification System at Netflix

- Ankush Gulati David Gevorkyan tl;dr: "In this blog post, we will give an overview of the Rapid Event Notification System at Netflix and share some of the learnings we gained along the way." Authors cover design decisions, architecture, observability and more. 

featured in #300

Building Robust Distributed Systems

- Kislay Verma tl;dr: "I have written before on this blog about what distributed systems are and how they can give us tremendous scalability at the cost of having to deal with a more complicated system design. Let’s discuss how we can make a distributed system resilient to random failures which get more common as the system gets larger."

featured in #299

The Internet Was Designed With A Narrow Waist

- Andy Chu tl;dr: A narrow waist is concept, interface, or protocol that solves an interoperability problem. Picture an hourglass with M things on one side, N on the other, and an important concept in the middle. Andy illustrates how IP is an example, and how that impacts internet architecture. 

featured in #299

Designing Netflix

- Ankit Sirmorya tl;dr: Ankit guides us through the architecture plan for a Netflix style application, planning for the following scale: 100 million active users registered, 2500 MB uploaded every minute, 10 combinations of resolution and codec formats supported, 3 videos watched daily.

featured in #290

Designing Instagram

- Ankit Sirmorya tl;dr: Ankit shows us how to architect an Instagram scale photo-sharing application where users can upload photos and view those photos, follow other users, view feeds containing posts of the users they follow, like and comment on posts.

featured in #289

Designing Uber

- Ankit Sirmorya tl;dr: Ankit shows us how to design architecture similar to Uber's: Riders are able to view available drivers in nearby locations, request rides from source to destination, notify nearby drivers of the ride and allow one of them to confirm the ride, show pickup ETA to customers when a ride is dispatched. 

featured in #287