Add outbox module: Transactional Outbox with the Spring Modulith Event Publication Registry

2026-10-03 19:27:32 +00:00
parent 866eceed0a
commit d815a37f2e
17 changed files with 721 additions and 0 deletions
@@ -0,0 +1,23 @@
+$ mvn -pl outbox -am test -Dtest=ReplayIncompletePublicationsTest
+(FlakyAuditListener throws on its first invocation of InvoiceIssued, succeeds on every
+ one after -- standing in for any downstream dependency that is briefly unavailable)
+
+Incomplete FlakyAuditListener publications after the simulated failure: 1
+Incomplete FlakyAuditListener publications after resubmission: 0
+Invoice 1 never changed -- the retry was purely about redelivering the event, the invoice row was correct the whole time.
+
+[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
+
+The sequence that actually ran: BillingManagement.issueInvoice() commits the Invoice
+row and the EVENT_PUBLICATION row for FlakyAuditListener in one local transaction.
+FlakyAuditListener.on(InvoiceIssued) is then invoked asynchronously, throws on purpose,
+and the registry leaves that row with COMPLETION_DATE still null -- "incomplete" is
+exactly that: a row with no completion date, regardless of whether the listener ever
+ran at all or ran and failed. Calling
+IncompleteEventPublications.resubmitIncompletePublicationsOlderThan(Duration.ZERO) --
+a real method on a real interface, verified against the compiled events-api 2.1.1 jar,
+not assumed from documentation prose -- re-invokes the listener for every such row.
+This time failNextAttempt is already false, so it succeeds, and the row's completion
+date is set. The invoice itself was never touched by any of this: the retry is about
+redelivering a notification, not about redoing a database write that already
+succeeded the first time.