In this article, I will share my thoughts on using centralised versus decentralised orchestration when building event-driven serverless systems. I have over 15 years of experience in designing and developing distributed event-driven systems. I have spent years migrating from monolithic systems to microservices and now to serverless-powered systems. Event-driven architecture can help build highly loosely coupled, fault-tolerant, scalable,… Read More »
This article discusses how leaders can use sprint retrospectives to build world-class engineering teams. By attending retrospectives and providing guidance and mentorship, leaders can help their teams to continuously improve their skills. Utilizing retrospectives is essential to the Agile process and can be a useful tool for building and maintaining high-performing teams. Leaders should encourage open and honest communication and create a safe environment so that teams can identify and address issues before they become more significant problems. Agile is not one-size-fits-all, and leaders must adapt their approach to meet their team’s needs.
Event-driven architecture is an approach to software design that relies on events to trigger actions. There are five primary patterns of event-driven architecture, including event-notification, event-carried state transfer, CQRS (Command Query Responsibility Segregation), event-sourcing, and event-streaming.
In the article I will describe what they are and the difference between Event-Streaming and Event-Sourcing