refactor: 리펙토링 진행중 의존성 gradle은 얇게 유지, 각 모듈에서 처리하고 있는 부분에 대해서 리펙토링
This commit is contained in:
@@ -88,10 +88,23 @@ consumer recovery가 동시에 나빠지고, 유계·검증 가능한 실패가
|
||||
## DB 마이그레이션
|
||||
|
||||
```text
|
||||
V1__messaging_outbox.sql
|
||||
V2__messaging_inbox.sql
|
||||
V1001__messaging_outbox.sql
|
||||
V1002__messaging_outbox_lease_fencing.sql
|
||||
V1003__messaging_admin_operation_journal.sql
|
||||
V1004__messaging_outbox_canonical_metadata.sql
|
||||
V1101__messaging_inbox.sql
|
||||
```
|
||||
|
||||
Messaging owns Flyway versions `1000..1999`. The starter assembles both JDBC reliability modules,
|
||||
so their migrations deliberately share `classpath:db/migration/messaging` but must never reuse a
|
||||
version. Keeping them in this reserved range also prevents collisions with the application's
|
||||
ordinary `db/migration/postgresql` stream, whose low-numbered versions are independent.
|
||||
|
||||
When adopting outbox/inbox persistence, add `classpath:db/migration/messaging` to the deployment's
|
||||
Flyway locations together with its normal application migration location. Do not copy or renumber
|
||||
these files into the application's low-numbered stream; the reserved range is the namespace
|
||||
boundary.
|
||||
|
||||
Outbox row는 business transaction과 같은 transaction에서 쓴다.
|
||||
Inbox reservation은 handler side effect와 같은 transaction에서 쓴다.
|
||||
별도 transaction이면 각 패턴이 닫으려던 창이 그대로 열려 있다.
|
||||
|
||||
Reference in New Issue
Block a user