View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight a series of posts on Modular Monolith architecture. I often shared articles on microservices, however, sometimes a module monolith may be more than enough for scaling organization and having multiple teams working on the same codebase.

Spotify Engineering shares with us their developer experience for Kubernetes using Backstage, one of the main open-source project coming out from the Swedish company.

Moving to microservices is far to be an easy journey, there are patterns that facilitate the transition, however, it's always good seeing what others are doing, like in this article from ThoughtWorks.

Are you working on a global platform that has to be tested end to end? If so this article from DAZN tech blog will provide a nice idea on how to test hundreds of countries on multiple devices without any queue at the airport.

Finally, one of the latest articles from Nick Tune regarding Domain Services with a focus on value generation.

Enjoy the read and see you next week!


Software Architecture

Modular Monolith: A Primer

Modular Monolith architecture is an explicit name for a Monolith system designed in a modular way.
To achieve a high level of modularization each module must be independent, has everything necessary to provide desired functionality (separation by business area), encapsulated and have a well-defined interface/contract.

Case Study

Designing a Better Kubernetes Experience for Developers

Backstage Kubernetes simplifies your deployment workflow by connecting to your existing Kubernetes implementation and aggregating the status of all your deployments into a single view — even across multiple clusters in multiple regions


Amortizing Software Rewrites: An Evolutionary Approach

How to rewrite legacy applications or split monoliths into microservices without slowing down on delivering features or introducing bugs in your system.

Case Study

How to QA the world

Service traffic is not the only capacity related problem. Manual operations such as setup or configuration soon start to bottleneck as the amount of work increases.
We needed to test the app globally and other than significantly upping the travel budget of our QA engineers we needed to think of a better solution.
Domain-Driven Design

Domain Services: The Next (small) Evolution of Microservices

Over the past couple of years, I’ve seen organizations referring to microservices as Domain Services. I’ve seen such benefits from this small reframing that I now recommend not using the word microservice and using Domain Service instead.

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