Dual-Orchestration Pattern Proposed to Separate Machine and Human Workflows in Banking
A technical paper published on DEV Community proposes a dual-orchestration architecture for modern core banking platforms facing conflicting execution demands. The approach, called the Xenon Architecture Standards, pairs Temporal for automated, low-latency distributed transaction workflows with Flowable for multi-week human approval and review processes. The design is mapped to Banking Industry Architecture Network (BIAN) service domains, assigning orchestration responsibility based on state duration, throughput, and human involvement. The paper argues that using a single orchestration engine for both profiles causes problems such as database bloat, thread starvation, and compromised audit compliance. Code examples illustrate how Temporal handles compensating transaction Sagas, including fund reservation, sanctions screening, and account crediting.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in