Building Resilient Event-Driven Microservices in Financial Systems with Muzeeb Mohammad

February 16, 2026·35 min·2 clips

Muzib Mohamed says RESTful APIs and SOAP systems hit speed-to-market and scaling limits, so JPMorgan Chase tried Kafka.

1. The InfoQ Podcast episode focuses on building resilient event-driven microservices for financial systems. 2. Thomas Betts hosts the conversation, and Muzib Mohamed joins as a senior manager of software engineering at JPMorgan Chase and a senior member of IEEE. 3. The episode asks how Kafka, microservices, and observability can replace slow monolithic processing in financial services. 4. Muzib contrasts RESTful APIs and SOAP-based web services with event-driven systems because the older stack struggled with time to market and scale. 5. He gives a SCI checking-account flow where customer data is published to Kafka topics for credit checks, fraud checks, and account opening. 6. The team says that async processing helped them meet the agreed SLA on that account-opening journey. 7. Muzib explains that separate Kafka topics and multiple consumers let fraud checking, credit scoring, and new-account creation run in parallel. 8. He says that decoupling let teams deploy independently and move from quarterly releases to on-demand deployments. 9. For reliability, the team uses trace IDs across the UI and microservices and inspects transactions in Splunk, Dynatrace, and AppDynamics. 10. He describes mainframe coexistence at SCI, where core checking and credit-card processing still run in mainframes. 11. One bridge pattern uses MQ: COBOL on the mainframe publishes to MQ, an MQ listener translates the message into a Kafka event, and downstream systems consume it. 12. Muzib says one use case around new credit cards and Priority Pass was created from that hybrid event-streaming approach. 13. He states that the long-term plan is to move away from the mainframe by building a system of record on the distributed side. 14. He says event streaming helps preserve a history of actions, such as a customer opening a checking account and later depositing money. 15. He also describes CDC change data capture from IMS and a Java-Spring reconciliation process that compares mainframe data with AWS public cloud data. 16. Muzib says the reconciliation reports have produced positive results and increased confidence in the distributed copy. 17. The tone is technical and practical, with Thomas asking process and migration questions and Muzib answering in implementation terms. 18. The format is a straightforward interview that moves from architecture patterns to migration, security, and AI. 19. Financial-technology architects planning mainframe-to-cloud transitions. 20. People looking for a high-level business or nontechnical discussion.

As heard by us

A practical look at event sourcing as a bridge from mainframes to resilient financial microservices.

Event driven microservices in financial systems are treated here as a migration path as much as an architecture choice. Thomas Betts keeps the conversation grounded with Muzib Mohammad, moving from account events and replayable histories to the problem of easing a mainframe out…

Read the full review in PlayNext →

Why you'd press play

For mainframe-heavy teams trying to make event-driven microservices traceable.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from The InfoQ Podcast