[Video Podcast] Building Resilient Event-Driven Microservices in Financial Systems with Muzeeb Mohammad

"So we actually do have a lot of applications built in the monolithic technology stack, like RESTful APIs, SOAP-based web services. But the challenges that we were facing is, I think, time to the market or to scale up the solutions, I think we were having some of the common challenges, the industry experiences. So we have tried some of the event-driven approaches. Very specifically we started with the Kafka as one of the architecture patterns."

"We started seeing a very good improvement. I will explain some of the examples that we successfully implemented at SEI. SEI was one of my previous employer. So part of when the customer tries to open a checking account, it goes through various systems behind the scenes. We were actually not reaching the SLA within the time. So what we did was we introduced a Kafka event-driven system in the backend processing."

Monolithic stacks using RESTful APIs and SOAP-based web services often face slower time-to-market and scaling difficulties. Event-driven architectures using Kafka can decouple backend processing, enabling asynchronous flows and independent scaling. Implementing Kafka as an architectural pattern reduced coupling and improved performance in complex, multi-system workflows. In a banking example, account opening processes that previously missed SLAs were restructured into Kafka-driven backend events, allowing services to handle steps independently and meet timing requirements. The pattern supports higher scalability, resilience, and faster delivery by isolating responsibilities and enabling parallel, observable processing across services.

Read at InfoQ