Welcome back to our weekly issue!
Let's start this issue with a case study on how to design API directly from Slack engineers. When we work on a platform that has to be maintained for several years with a large audience, having some guardrails for designing our APIs can help to create consistency despite the number of teams working on different domains.
Nick Tune reminds us of the importance of designing the correct data model for structuring our projects. But this time, Nick surprised everyone using the hidden gems in chapter 8 of Eric Evans' book.
It was a while without sharing some content from one of our favourite architects out there: Mark Richards. This is an episode every architect should listen to because there are 60 minutes of suggestions to become a great architect.
We finish this issue with two case studies, the first one covers the challenges of working with burst traffic and how to design your infrastructure for handling the scale properly, the second one covers a great idea on how to create architecture groups inside an organization. In both cases plenty of great ideas to use immediately inside our teams.
Enjoy the read and see you next week!