A 16-microservice trading platform matching buyers and sellers across multi-tenant e-waste categories, run at 99.9% uptime.
I architected the platform as the lead developer at Opal BPM: I designed the service decomposition, made the core data and messaging architecture decisions, and led implementation across the microservice set. This was built and delivered under my technical ownership, not handed to me as a pre-defined spec.
Decompose the platform into 16 focused microservices rather than a smaller number of broader services.
Why — Order intake, trade matching, settlement, and notification have distinct scaling and change profiles per tenant and waste category — separating them let each evolve and scale independently.
Tradeoff accepted — More services to operate, deploy, and monitor, and more discipline required in inter-service contracts and versioning.
Use Kafka as the backbone for order-to-settlement event flow.
Why — Trade matching and settlement are inherently event-driven (an order placed, matched, and settled is a sequence of state transitions across services) — Kafka gives durable, ordered delivery and lets notification consume the same event stream without coupling to the transactional path.
An RFC 1.2.0-compliant Beckn adapter ("WRI Connector") for identity verification across multiple providers, with sub-50ms P95 latency.
A standardized OAuth2 authentication and authorization system rolled out across multiple client deployments of Opal's platform.