Problem
Payment events were coupled through synchronous calls across a three-framework backend, so ordering and replay were not guaranteed.
Approach
Introduced Kafka event-driven service-to-service communication.
Outcome
Qualitative
A payment gateway built across three backend frameworks. The architectural move that mattered was replacing synchronous service-to-service calls with Kafka: payment events became ordered and replayable instead of a chain that fails halfway.
What I did
- Introduced Kafka event-driven service-to-service communication across a three-framework backend so payment events stayed ordered and replayable rather than coupled through synchronous calls.
- Guided the Flutter team through complex floating UI components and secure payment-gateway integration, including dynamic form handling for 50+ input fields in a single component.
Stack
Screens
More work
SystemsSource?. Manga
A digital manga and video streaming platform.
SystemsRyobi
Concurrent Japanese enterprise projects — city council services, agri-business portals, milk collection and distribution, and hospital management.
SystemsAgave
A Japanese e-commerce platform for buying and selling plants.
Building something that needs this kind of engineer?
Hiring, contract, or an architecture problem — tell me the shape of it and I’ll come back with something specific.