Fundamental Software Architectural Patterns
tl;dr: "Patterns are essentially reusable solutions to common problems. When faced with a problem it is reasonable to consider a catalog of patterns in order to find suitable existing solutions before designing something entirely new. Then, it will be a matter of adapting these patterns to the scope of our reality." The author discusses client server, pipe and filter, SOA patterns, and more.featured in #334
How We Built Infrastructure to Run User Forecasts At Spotify
- Molly Zhu tl;dr: "To enable fast iterations and facilitate model training, we built a system that allows user forecasts to run both on demand and automatically every week, with the heavy hyperparameter tuning part running on the weekend. The system creates visualizations and automated insights to surface information, and provides easy-to-use tools for manual interventions for both data scientists and business stakeholders."featured in #332
Effective Microservice Communication And Conversation Patterns
- Jimmy Bogard tl;dr: "In this talk we'll look at the problem from a holistic perspective - take the fundamental property of autonomy for any microservice-based architecture, and design how services should communicate so that they can still achieve their purpose in the world."featured in #327
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
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