Crane: Uber’s Next-Gen Infrastructure Stack
tl;dr: "Uber has been on a multi-year journey to reimagine our infrastructure stack for a hybrid, multi-cloud world. The internal code name for this project is Crane. In this post we’ll examine the original motivation behind Crane, requirements we needed to satisfy, and some key features of our implementation. Finally, we’ll wrap up with some forward-looking views for Uber’s infrastructure."featured in #381
McDonald’s Event-Driven Architecture: The Data Journey And How It Works
- Vamshi Krishna Komuravalli Damian Sullivan tl;dr: Here is a typical data flow of how events are reliably produced and consumed from the platform: (1) Initially, an event schema is defined and registered in the schema registry. (2) Applications that need to produce events leverage producer SDK to publish events. (3) When an application starts up, an event schema is cached in the producing application for high performance. The authors continue to discuss how data flows through the system.featured in #380
Architecture Diagrams Should Be Code
- Brian McKenna tl;dr: "Architecture code can be versioned with the code which implements it. We can write algorithms to check our architecture. I’d like to see more tools available to describe architecture as part of code, allowing us to generate as many diagrams as we want, for accurate and easy communication."featured in #380
Reverse Engineering TikTok's VM Obfuscation (Part 1)
tl;dr: "The platform has implemented various methods to make it difficult for reverse-engineers to understand exactly what data is being collected and how it is being used. Analyzing the call stack of a request made on tiktok can begin to paint the picture for us."featured in #379
Devpod: Improving Developer Productivity at Uber with Remote Development
tl;dr: "In this blog, we share how we improved the daily edit-build-run developer experience using DevPods, our remote development environment. We will start with some of the initial challenges, the pain points we addressed with Devpod, our architecture, and some of our recent successes in terms of adoption and cost reduction. We will finally leave you with some thoughts around the future of remote development at Uber."featured in #377
featured in #376
The GPT-3 Architecture, On A Napkin
- Daniel Dugas tl;dr: "There are so many brilliant posts on GPT-3, demonstrating what it can do, pondering its consequences, vizualizing how it works. With all these out there, it still took a crawl through several papers and blogs before I was confident that I had grasped the architecture. So the goal for this page is humble, but simple: help others build an as detailed as possible understanding of the GPT-3 architecture."featured in #375
Deduping And Storing Images At Uber Eats
- Kristoffer Andersen tl;dr: "The Uber Eats system handles several hundred million product images and millions of image updates are performed every hour. We have implemented a content-addressable caching layer that very effectively detects duplicates and thereby reduces download times, processing times, and storage costs."featured in #374
Free O'Reilly book: Identity-Native Infra Access
tl;dr: Download the first chapters of the latest O’Reilly book and learn how to prevent breaches by eliminating secrets and moving to an entirely passwordless infrastructure.featured in #373
Simplifying Developer Testing Through SLATE
tl;dr: "Testing a service in isolation (i.e. unit, integration, component tests) is important as it gives faster feedback to developers. But to validate whether the requirements for a service are met with the current state of dependencies and get confidence, developers rely on E2E testing. This article describes how we enabled E2E tests for developers with improved dev experience."featured in #373