Add order-fulfillment module: Spring Modulith 2.1 boundary enforcement, events, generated docs

2026-10-03 18:45:37 +00:00
commit 866eceed0a
34 changed files with 1149 additions and 0 deletions
@@ -0,0 +1,27 @@
+spring.application.name=order-fulfillment
+
+spring.datasource.url=jdbc:h2:mem:modulith;DB_CLOSE_DELAY=-1
+spring.datasource.driver-class-name=org.h2.Driver
+spring.jpa.hibernate.ddl-auto=update
+spring.jpa.open-in-view=false
+
+# Spring Modulith's JDBC/JPA event publication registry creates its own table
+# on top of whatever schema-generation strategy is already in play.
+spring.modulith.events.jdbc.schema-initialization.enabled=true
+
+# Republish anything left PUBLISHED/PROCESSING by an unclean shutdown.
+spring.modulith.events.republish-outstanding-events-on-restart=true
+
+# NOT enabled for this demo (left commented so the defaults above are what actually ran
+# for every captured transcript in output/). In production, turn these on:
+#   spring.modulith.events.staleness.published=PT5M
+#   spring.modulith.events.staleness.processing=PT5M
+#   spring.modulith.events.staleness.resubmitted=PT5M
+#   spring.modulith.events.completion-mode=ARCHIVE
+# Without them: completed rows accumulate forever (completion-mode defaults to UPDATE,
+# which never deletes), and a row stuck in PUBLISHED/PROCESSING after a crash has no
+# staleness monitor to mark it FAILED and eligible for resubmission -- all three
+# staleness durations default to zero, which this library treats as "off".
+
+logging.level.com.ankurm.modulithdemo=INFO
+logging.level.org.springframework.modulith=INFO