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…
How integration patterns impact your microservices architecture
When the world wide web first emerged, integrating different types of operating systems was a core challenge. Hypertext transfer protocol (HTTP) created communication channels by sharing hypertext, these systems started speaking a common language over an accepted protocol, and the…
Principles for microservices integration
Out of the many advantages of microservices, the most significant motivations are scale and autonomy for business units. These go hand in hand. However, we still need to create an integrated experience that makes sense for the end user. It’…
Business case for observability
In the previous post [https://aradhye.com/increasing-observability-of-microservices/], we took a look at what observability is and how to build it into your application. Just to recap, observability is developing insights into the system based on external signs. For example,…