Copy
View this email in your browser

Dear Architect,

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!

In the SPOTLIGHT

Case Study

How We Design Our APIs at Slack

Over the years, one thing we keep top of mind is designing for a great developer experience. While we can change the implementation of our features under the hood, removing or changing the behavioral contract for an existing API is very hard. That’s why it’s important to carefully think about your API design from the very beginning. 

Domain-Driven Design

Share Pie: The DDD Treasure Hidden in Plain Sight

There’s an aspect of Domain-Driven Design that rarely gets talked about. I think it’s the most important aspect of DDD, yet if you search online for “Domain-Driven Design”, you won’t find it. This treasure has been hiding in plain sight all along. It’s the Share Pie story in chapter 8 of Eric Evans’ DDD book.

Software Architecture

Mark Richards On Software Architecture

I had the pleasure of sitting down to speak with Mark Richards, author, trainer, coder and software solution architect. We discuss everything from agile architecture methods, modern software architecture patterns to business value and technical debt.

Case Study

To Scale In Or Scale Out? Here’s How We Scale at Dream11

Autoscaling in terms of infrastructure, has several limitations. Its provisioning time is not fast enough to support the compute requirements for users during key events! A flood of users during tsunami traffic needs short provisioning time to keep up with the spike, and it may not be suitable to have a build time and make users wait.

Software Architecture

Software Architecture for Scale-ups

You’re part of a small start-up. There’s only one thing on your mind: shipping a product and rapidly finding product-market fit. Code is king! Software architecture? Sounds like a quaint concern from people who don’t ship. But, as it turns out, every system has an architecture

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

HELP US TO IMPROVE THIS NEWSLETTER!
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!
Twitter
Website
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