Copy
View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week, in the spotlight we have a fantastic podcast on microservices and how to minimise coupling at different stages (design, runtime and infrastructure coupling). The constant reminder of Conway's law during this episode was absolutely fabulous.

Ephemeral environment for testing is a great practice that nowadays are easier to create thanks to the agility provided by cloud providers, containers and infrastructure as code. Check out this case study at Paystack using Kubernetes for creating on-demand environments.

Event Storming is a technique that I highly recommend to understand and master because it can really help not only during migration from monolithic to microservices architecture but also for evolving your current architecture.

Very interesting article from Capital One sharing how to design API for fast evaluation of their usage bearing always in mind the product we are building.

Finally a talk on distributed systems and the trade-offs we have to make in order to achieve our goals.

Enjoy the read and see you next week!

In the SPOTLIGHT

Microservices

Design-Time Coupling in Microservices

In this episode of the InfoQ Podcast, Thomas Betts speaks with Chris Richardson about minimizing design-time coupling in a microservice architecture. Chris begins by defining design-time coupling, and contrasts it with runtime coupling. We then discuss some of the problems that arise from design-time coupling, anti-patterns and symptoms that are warning signs of high coupling, and the trade-offs that architects need to consider in their designs.

Case Study

Building on-demand staging environments at Paystack

Here, we’ll share how we leveraged Kubernetes to create these on-demand environments in a bid to reduce deployment time and improve developer efficiency.

Microservices

Decomposing the Monolith with Event Storming

As software engineers and architects, we are often faced with the challenge of creating a target microservices architecture for a legacy system. These systems are often big monolithic applications that have been around for years, often with lots of dependencies, and usually with no one person in your company that understands it all

API design

Design Thinking and API Design

Experimental APIs are mock services that use simulated data to mimic API functions. They are designed with the goal of getting early feedback from the community around API desirability and design before the product release.
Distributed Systems

Essential Complexity in Systems Architecture

Laura Nolan looks at some real distributed system architectures and examines the tradeoffs made, showing how simple systems can create complex and difficult to understand behaviors.

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