View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week, in the spotlight a case study on moving 4000 repositories to GitHub actions directly from the DX team of DAZN. Ok, these kinds of transitions are not happening every day, however from this case study we can definitely learn something useful to apply today or in the near future.

It was a while without sharing a good video on Domain-Driven Design, this one, in particular, is very interesting because it covers how to communicate between bounded context using events.

Then I really enjoyed reading the solutions shared by Airbnb engineering teams, the first on how to create a cross-platform UI totally server-side driven. The second one how to handle complex transactions using idempotent APIs.

Finally, Spotify tech teams started a series of posts on how they handle any event coming from a client device to their infrastructure, all the challenges they are facing and, most importantly, how they have overcome them.

Enjoy the read and see you next week!



A Tale of Moving 4000 GitHub repositories to GitHub Actions

At DAZN, we’ve just finished the first few phases of our large-scale migration of 4000 code repositories to GitHub Actions.

Today we want to take you through that process, and share with you some of the challenges that we faced.

To start, let’s begin with some context…

Domain-Driven Design

Practical DDD: Bounded Contexts + Events => Microservices

Indu Alagarsamy talks about the intersection of DDD as a software discipline with Messaging as a technology counterpart. DDD allows us to move faster and write high-quality code. When we start to use the technology of messaging to communicate between clean and well-defined bounded contexts we get to remove temporal coupling

Case Study

A Deep Dive into Airbnb’s Server-Driven UI System

What if clients didn’t need to know they were even displaying a listing? What if we could pass the UI directly to the client and skip the idea of listing data entirely? That’s essentially what SDUI does — we pass both the UI and the data together, and the client displays it agnostic of the data it contains.

Case Study

Avoiding Double Payments in a Distributed Payments System

There are three different common techniques used in distributed systems to achieve eventual consistencyread repair, write repair, and asynchronous repair. There are benefits and trade-offs to each approach. Our payments system uses all three in various functions.

Case Study

Spotify’s Event Delivery

Whenever a user performs an action in the Spotify client—such as listening to a song or searching for an artist—a small piece of information, an event, is sent to our servers. Event delivery, the process of making sure that all events gets transported safely from clients all over the world to our central processing system, is an interesting problem

Thanks for reading Dear Architects 🙏

If you have any suggestions to make this newsletter better, just drop us an email!

Have a great rest of the week 😉

Opinions are my own

We just need a few minutes of your time to make Dear Architects even better
Sure! Let me share what I think about Dear Architects!
Copyright © 2021 deararchitects, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp