Enterprise integration patterns, choreography vs orchestration, canonical data models, and adapter design for complex financial ecosystems — with the runtimes that implement them in production.
Eliminating the N×M mapping explosion across ISO 20022, SWIFT MT, SAMA Open Banking, and legacy core formats: entity taxonomy, Java 21 CDM implementation, IBM ACE JavaCompute wiring, Apache Camel TypeConverter binding, schema versioning strategy, and the governance model that keeps the canonical alive when SAMA ships a spec update.
The single most under-implemented pattern in financial-services APIs: key design, storage trade-offs (Redis vs Postgres vs hybrid), TTL and eviction, request-fingerprint matching, replay semantics, and the production failure modes that turn a retry into a duplicate payment.
The EIP catalogue applied to production: content-based router, message translator, splitter, aggregator, and how IBM App Connect Enterprise implements them in real flows behind the bank.
Camel K and Camel Quarkus on OpenShift: the three runtime modes, route DSL trade-offs, financial services connector catalog, mTLS & OIDC wiring, and the honest comparison with IBM ACE and MuleSoft Anypoint.
Mapping legacy SWIFT MT103 and MT202 messages to ISO 20022 pacs.008 and pain.001 flows in a KSA bank: translation architecture, IBAN enrichment, SAMA IPS mandatory extensions, the coexistence strategy for the CBPR+ parallel-run window, and the truncation traps that cause silent rejects.
ACE ESQL fan-out/fan-in aggregator, Spring Boot CompletableFuture composition with Resilience4j circuit breakers, Open Banking BFF design, timeout budget allocation, partial result handling, and the BFF-layer caching patterns that reduce downstream load.