In part 1 of our microservices readiness series [https://aradhye.com/are-you-ready-for-microservices-pt-1-need-alternatives-and-ability/] , we looked at how we determine if microservices is actually the right route for you. Once you’ve identified an actual need, ruled out alternative options as insufficient,…
Architecture
A collection of 4 posts
Are you ready for microservices? Pt 1: Need, alternatives, and ability
As a development team, our goal is to deliver software that solves business problems. The business’ goal is to provide value to the customers as quickly as possible. “Monolith to microservices” is not a business goal. Business stakeholders don'…
Refactoring the Architect's Role - What is Architecture?
Previously [https://aradhye.com/refactoring-the-architects-role-smells/], we saw the smells or the problems related to the architect's role. These legos represent one of them. They represent a lot of software architectures I see. Too many items and can'…
Refactoring the architect's role - The smells
The autonomy that comes with microservices is very attractive to our customers. Sometimes it starts to become a double-edged sword of sorts. They realize that the power of autonomy comes with a great responsibility for the development teams and the…