- 결정 10: consume 계약을 `MessageHandler<T>` 하나로, starter-kafka가 consumer 조립(handler bean이 있으면 켜짐, `app.messaging.enabled=false`로 끔). 오프셋은 handler Success(inbox면 트랜잭션 커밋) 뒤 또는 DLQ 쓰기 확인 뒤에만 커밋, auto-commit 금지, `read_committed`, 재시도 소진 → DLQ(없으면 멈춤) — Kafka+PG로 왕복·중복 제거·DLQ 검증 - 미사용 API 타입·Blocking/Reactive/Batch facade·reactor api 노출 삭제, `PublishResult` 정적 factory, `MessagingCapabilities` → EnumSet, API leaf 병합(core-api+schema-api, admin-api+admin-runtime), starter god config 분해, Kafka broker 설정은 starter-kafka로, 등급 용어 정리 - 결함 수정: Retry 응답이 시도 횟수를 세지 않아 partition 정지(P21-new-1), deliveryAttempt 항상 1(P21-new-2) - 통합: app-bootstrap `MessagingPublicSurfaceContractTest` 기대값을 P21 변경에 맞춤, starter-kafka에 `api kafka-clients` 검증: ./gradlew check architectureCheck verifyDependencyLocks :app-bootstrap:verifyEnvKeys :app-bootstrap:integrationTest :sample-portfolio:integrationTest :messaging:messaging-spring-boot-starter:integrationTest :messaging:messaging-reliability-jdbc-postgresql:integrationTest mainCheck --continue 통과(812 task) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
44 lines
1.8 KiB
Groovy
44 lines
1.8 KiB
Groovy
plugins {
|
|
id 'ca.auxiliary-source-set'
|
|
id 'ca.platform-module'
|
|
}
|
|
|
|
auxiliarySourceSets {
|
|
sourceSet('integrationTest') {
|
|
compilesAgainst 'main'
|
|
}
|
|
}
|
|
|
|
// The relational implementations of the reliability ports: the outbox repository, the inbox
|
|
// repository and the destructive-operation journal. Spring JDBC for the transaction join, and SQL
|
|
// that is PostgreSQL's (`jsonb`, `FOR UPDATE SKIP LOCKED`, `ON CONFLICT`, `TIMESTAMPTZ`) — the name
|
|
// is the contract. The relay and consumer logic that uses them is messaging-reliability.
|
|
dependencies {
|
|
api project(':messaging:messaging-core-api')
|
|
api project(':messaging:messaging-reliability-api')
|
|
|
|
// The destructive-operation journal lives here because it needs exactly what the outbox needs:
|
|
// one relational database every replica can see, and a migration lane that already exists. The
|
|
// contract it implements belongs to the admin API.
|
|
api project(':messaging:messaging-admin')
|
|
|
|
implementation 'org.springframework:spring-jdbc'
|
|
implementation 'org.springframework:spring-tx'
|
|
|
|
// Live-database certification. The reliability patterns are claims about transaction
|
|
// boundaries and uniqueness constraints, and only a real database can settle them.
|
|
testImplementation project(':messaging:messaging-testkit')
|
|
integrationTestImplementation project(':messaging:messaging-testkit')
|
|
integrationTestImplementation 'org.testcontainers:testcontainers-postgresql'
|
|
integrationTestImplementation 'org.testcontainers:testcontainers-junit-jupiter'
|
|
integrationTestImplementation 'org.postgresql:postgresql'
|
|
}
|
|
|
|
strictTestLanes {
|
|
lane('integrationTest') {
|
|
integration()
|
|
sourceSet = 'integrationTest'
|
|
description = 'Runs outbox, inbox and admin-journal contracts against real PostgreSQL.'
|
|
}
|
|
}
|