How ironbats/bpm-order-mngmt-system works
Project type and purpose
• This is a backend‐focused, BPM-driven Order Management microservice.
• It uses Spring Boot for the API and business logic, Camunda BPM for process orchestration (BPMN workflows), Kafka for event-driven communication, and Docker for containerization.
File structure
• Top level:
• docker/compose-ui (Camunda UI + tools)
• docker/compose (service + Kafka + DB)
• src/main/java/com/bpm – packages for controller, service, repository, events, Camunda delegates, configuration.
• src/main/resources – application.yaml (configs), BPMN files (order-service-v4.bpmn, process.bpmn).
• Key patterns:
• Layered architecture (controller → service → repository)
• Event-driven sub-package (KafkaEventProducer/Consumer)
• BPM delegates (OrderCreated, OrderCancelled, incident handlers).
README
• Confirms tech stack: Camunda, Java 21, Spring Boot, Kafka, Docker.
Detail without over-splitting
• Package group (controller, service, repository, events, Camunda tasks) as its own component.
• Both the process definitions (.bpmn files) and their runtime host (Camunda engine).
• Database once, but annotate that it serves both the repository and the Camunda engine tables.