/Architecture

Demystifying Software Architecture Patterns

- Rahul Garg tl;dr: "The 3 most talked about patterns are Clean, Hexagonal, and Onion Architecture... all define a loosely coupled testable system that avoids any direct dependencies in terms of implementation, yet do so using their own terminology and each with specific nuances. They all suggest approaches to make software architectures more manageable and testable." Rahul looks at each as well as key architectural takeaways applicable regardless of approach.

featured in #358

What It Took To Scale Spotify’s Marketing Efforts

- James La Broy tl;dr: "More recently, we wanted to run more campaigns throughout the year, perhaps during different holidays like Halloween or Easter. Rather than having one centralised team configuring campaigns across multiple markets, we wanted to create distributed teams local to each individual market responsible for tailoring campaigns to their respective audiences." James discusses the changes that enabled this to happen. 

featured in #354

Event Driven Architecture - 5 Pitfalls to Avoid

- Natan Silnitsky tl;dr: (1) Write to db and then fire event without atomicity. (2) Using event sourcing everywhere. (3) No context propagation. (4) Publishing events with large payloads. (5) Not handling duplicate events.

featured in #347

Under The Hood: How We Built API Versioning For LinkedIn Marketing APIs

- Nihit Purwar tl;dr: "We were releasing breaking changes almost monthly with different sunset dates – making it hard for developers to test and plan their roadmap without a predictable release schedule. Unversioned APIs also blocked customers from accessing the latest features and caused internal challenges with new feature development." Nihit's discusses how his team set out to build API versioning for LinkedIn Marketing APIs.

featured in #346

Pricing At Lyft

- Yanqiao Wang tl;dr: "In this blog post, we discuss the rideshare pricing system architectural design, modeling approaches and potential future iterations of Lyft’s pricing engine to illustrate how we tackle price optimization to achieve Lyft’s long-term mission."

featured in #342

You Don’t Need Microservices

- Matthew Spence tl;dr: "The monolith should remain the default choice for new, small, and medium-sized engineering teams. Microservices are still an option, but you should have compelling context-specific reasons to justify their use." 

featured in #339

Revert To Source

tl;dr: "In many organizations, once the work has been done to integrate a new system into the mainframe, it becomes much easier to interact with that system via the mainframe rather than repeat the integration each time." this leads to a "legacy system becoming the single point of integration for multiple systems, and hence also becoming a key upstream data source for any business processes needing that data."

featured in #335

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