/Architecture

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

Designing Tinder

- Ankit Sirmorya tl;dr: Ankit shows us how to design the architecture for a global Tinder-like service where users can create profiles, view recommendations of other users in geographically nearby regions, like or dislike other recommended users, get notifications when matched and be able to move to a different location and still get recommendations of nearby users.

featured in #286

Designing WhatsApp

- Ankit Sirmorya tl;dr: Ankit shows us how to design such a system factoring in such scale: 1 Billion users on the application per month, 650,000 active users per second at peak, 40m messages per second at peak. "The entire application will comprise of several microservices each performing a specific task." 

featured in #285

Processing Billions Of Events In Real Time At Twitter

- Lu Zhang Chukwudiuto Malife tl;dr: "We process approximately 400 billion events in real time and generate petabyte (PB) scale data every day." The authors discuss existing challenges with the current architecture, new architecture, and how they evaluate performance.

featured in #275

An Intro To Designing Secure CI/CD Pipelines

- Juho Nurminen tl;dr: An introduction to how high-level infosec design principles apply to CI/CD, and some technical tips on securely configuring CI pipelines.

featured in #272

Behind The Scenes, AWS Lambda

- Bruno Schaatsbergen tl;dr: "Lambda is split into a control plane and data plane. Each plane is responsible for a specific set of activities in the service. The Control Plane provides management APIs and manages integrations with all AWS services. Whilst the Data Plane is Lambda's Invoke API that triggers Lambda function invocations, this explanation is still very abstract but things will become clearer over time." Bruno details the underlying mechanics of AWS Lamda. 

featured in #271

On Making Architectural Decisions

- Evgeniy Nikonorov tl;dr: Here we are shown that the architect’s main task is to define the comprehensive context - a set of evaluation criteria - to make well-balanced architectural decisions, and how to go about doing so.

featured in #252

ARCHITECTURE.md

- Alex Kladov tl;dr: It takes 2x more time to write a patch if you are unfamiliar with the project, but 10x more time to figure out where to change the code. "ARCHITECTURE.md is a low-effort high-leverage way to bridge this gap." Aleksey gives us an example.

featured in #224