About This Architecture

Event-driven banking transaction system built on OCI using Spring Boot microservices, Apache Kafka async messaging, and Camunda BPM workflow orchestration. Frontend Application routes transaction requests through Transaction Service, which validates balances via Saldo Service before publishing approval or denial events to Kafka topics. MongoDB persists transactions, Redis provides atomic locks and caching, while New Relic APM, distributed tracing, and centralized logging ensure full observability across REST, Kafka, and Camunda flows. This architecture demonstrates fast-fail validation patterns, saga-based transaction orchestration, and real-time notifications via Kafka Consumer and Server-Sent Events. Fork and customize this diagram on Diagrams.so to adapt workflow steps, add additional microservices, or integrate alternative observability platforms.

People also ask

How do you design a scalable banking transaction system with event-driven microservices, workflow orchestration, and real-time observability on OCI?

This diagram shows a complete banking transaction architecture using Spring Boot microservices for transaction, balance, and notification services, with Apache Kafka for async event publishing (approval/denial), Camunda BPM for workflow orchestration, MongoDB for persistence, Redis for atomic locks, and New Relic APM for distributed tracing and centralized logging across all services.