Spring Batch restarts preserve committed work, while a Modulith package check constrains which classes another module may call.
Review the boundaries
- Spring Batch job identity: a manifest ID defines restart versus a new run
- Spring Batch chunks: a later failure does not erase an earlier commit
- Spring Batch writers: use a stable source key when a chunk is replayed
- Spring Batch skip and retry policy: distinguish bad input from temporary failure
- Spring Modulith module APIs: call the inventory root package, not its internals
- Spring Modulith verification: a compiling internal import still fails architecture checks
- Spring Modulith events: publish a domain fact after a valid state change
- Spring Modulith module tests: distinguish structure verification from a sliced context
Check your reasoning
Answer each question and inspect the explanation. This browser self-check does not run a production database or event broker.
Common Mistakes
A saved cursor does not prove exactly-once output, and a package check does not prove runtime delivery.