Copy
View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

API API API, sometimes we forget the importance an API plays in the grand scheme of things, this case study from PagerDuty gives their take on how to revitalise API inside your organization.

Cloud migrations are not easy, and there are many workloads out there that could benefit from it. Check out this post on how to successfully migrate to the cloud keeping without always start from scratch.

In the past few weeks, I spent a bit of my time deep-diving into GitOps, MLOps and AIOps, so I thought would be great to share an article or two about these interesting topics considering they can really help when you are dealing with infrastructure or AI/ML workloads.

This article on DDD was quite pragmatic, I shared many times DDD article was very dogmatic but this one was spot on to explain that DDD should be used in your architecture but don't be obsessed with it, there is always time for refactoring and changing your decisions.

Distributed systems are not providing only technical challenges but also (mainly maybe?) organizational ones, how you design architecture will reflect within your organization and the other way around. In this opinionated article, there is a clear emphasis on enforcing the teams' boundaries for decentralising the decision making and allowing every team to move at their own pace.

Enjoy the read and see you next week!

In the SPOTLIGHT

Case Study

Revitalizing API development at PagerDuty

API contracts are essentially set in stone, and adding, changing, or iterating on them is often cumbersome and difficult. API change processes themselves can be frustrating and slow, and mistakes can be extremely costly. But as a product’s functionality grows, so should its API—so having well-defined and well-working change processes is vital to a business.

Cloud

3 Phases to a Safe and Successful Cloud Migration

This three-phased approach enables organizations to take advantage of cloud benefits like capacity on-demand and matches to many Agile software development best practices. It speeds up many engineering, QA and dev/test processes by allowing teams to work simultaneously while reducing risk by not re-platforming or rearchitecting during the migration and by tackling that work in small, manageable increments.

DevOps

Why Should We Care about AIOps?

Now your problems really start, as it turns out the actual AI code is often the smallest part of the whole project. You need to expand your already complex DevOps pipeline to ship not only code but also stochastic black boxes.

Domain-Driven Design

The Domain Driven Design’s Missing Pattern

Most of the mid/large applications are a perfect field to explore with DDD approach. Doing DDD, though, doesn’t just mean blindly applying patterns and concepts. It’s more about the way you gain knowledge and how you use this knowledge to make your architecture evolve.

Team Topologies

Better coordination, or better software?

When different parts of an organization need to coordinate, it seems like a good idea to help them coordinate smoothly and frequently. Don’t. Help them coordinate less — more explicitly, less often.

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