An empty mind is an engineer's workshop. That saying is as old as time. Two things happened simultaneously in 2020 - The Pandemic hit, causing many jobs in IT to move from working from the office to working from home. We were expecting a baby and therefore had to take additional precautions, which meant a complete disconnect from human civilization, barring the occasional video calls. The second thing during this period was moving into a brand-new flat. As you scour through manuals from Ikea, you start understanding the patterns. You can see which manual is copy pasted from other manuals; you can empathize with the manual-making team and how overworked they are to churn out new assembly guides for every new piece of furniture in the market. That was when I looked at the house carefully and asked a pertinent question, why in the 22nd century, do we need switches? The light control is a stone-age activity; you move from your position, drop what you are doing, reach this non-descript ...
Posts
In Microservices architecture, we break down large monolithic applications into small, independent services that are developed and deployed independently. Each service is focused on a specific business function and can be scaled and updated separately. Event-driven microservices architecture is a pattern based on asynchronous communication between microservices. The microservices communicate with each other by emitting and consuming events. Example Consider a simple object model below: Add alt text Simple object model Benefits of Event-Driven Microservices An event-driven microservices architecture provides several benefits over traditional architectures. Some of these benefits include: Loosely coupled: Event-driven microservices architecture allows services to be loosely coupled, meaning each service can operate independently without knowing about the other services. Scalability: Event-driven microservices architecture enables services to be scaled independently, which allo...