View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week, in the spotlight some fantastic notes from Eduardo da Silva who opens up the pandora's box, where architects fit inside an organization. There are different strategies that can be embraced and I love the cross-references with other ideas from other authors. I think the best resource I read this week.

Design patterns come very handily when you are migrating your monolithic code base to microservices, here a set of useful patterns that can be applicable to your migration.

My colleague Seth Eliot shares his experience on disaster recovery in this series covering all the different approaches available. From a simple backup and restore to a more complex active/active architecture. DR can have a strong impact on your architecture, knowing the business intentions can help you to figure out the best strategy for your context.

I found interesting this article from the Tableau engineering team regarding how to reduce the knowledge gap across teams. I think in large organizations looking at the communication flow and enhancing where needs is a must-have for delivering high-quality software.

Finally, after a while, I found a case study on monitoring. This post with real experience from the trenches should provide you with some ideas applicable to your projects.

Enjoy the read and see you next week!


Socio Technical Architecture

Architecture Topologies & Architecture as Enabling Team

The topologies (models/forms) that we can adopt to approach architecture is a rather relevant topic since whether one likes it or not every system has an architecture. It may be explicitly or implicitly addressed, however saying we have no time for it, is a trap and recipe for "messy situations".

Design Patterns

Patterns to know before migrating your monolith to microservices

It turns out, migrating to microservices isn’t that easy. The first question you should ask is, do you really need microservices. Many problems of the monolith can be fixed easily by using modular monolith architecture. Once you have become sure that you want microservice, you have to create a plan to convert monolith into microservices. There are some patterns that can help you to create the required plan.

Disaster Recovery

Disaster Recovery Series

In my first blog post of this series, I introduced you to four strategies for disaster recovery (DR). My subsequent posts shared details on the backup and restore, pilot light, and warm standby active/passive strategies.

Engineering Practices

Architecture Review Across Teams

How do you get information out of one person’s head and into everyone else’s? Ask a software engineer to give a one-hour brown bag presentation, scheduled weeks in advance? How does anyone even know what information would be useful?

How we monitor the health of our applications and infrastructure

Having the visibility into these metrics of our application provides us with a starting point and baseline to continually improve on. Quoting father of management consulting Peter Drucker, “If you can’t measure it, you can’t improve it”.

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