- pub/sub 표면 삭제(G-6b·G-4i — 소비자 0, capability 규칙 3): SDK pub/sub·runtime gateway·PUBSUB lane·env 키 2개 - runtime을 `…cache.redis.runtime`으로(split package 해소), runtime은 소비자가 쓰는 8개 명령(`SemanticRedisCommands`)만, 118개 메서드 gateway는 redis-sdk가 확장. SDK의 blocking·transaction·admin lane은 코드로 조립(env 키 4개 삭제) - EVALSHA+NOSCRIPT 재로드 헬퍼 하나(메시지에만 NOSCRIPT가 온 경우도 재로드 — `LeaseScriptsTest` FAIL→PASS) - startup rule 목록 + runner 하나(환경 검사 8개, exit code·문구 유지), Redis secret 요구는 모듈이 기여, ratelimit 정책을 cache-redis 밖으로, lease fencing 계약 테스트(fake·어댑터·실제 Redis) - 통합: redis-sdk 테스트 2개가 옛 split package 경로를 보던 것 수정(ORCH-new-4) 검증: ./gradlew check architectureCheck verifyDependencyLocks :app-bootstrap:verifyEnvKeys configContractCheck :app-bootstrap:integrationTest :sample-portfolio:integrationTest :sample-portfolio:systemTest --continue 통과(682 task), Redis 7.4 standalone topology lane: runtime 7 · sdk 14 · cache-redis 19, 실패·skip 0 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
7.5 KiB
7.5 KiB
app-bootstrap — application entry point & composition root
Registered identity
- Module ID:
app-bootstrap - Gradle path:
:app-bootstrap - Focused test (derived from Gradle path):
./gradlew :app-bootstrap:test --console=plain - Runtime baseline: Java 21; repository framework baseline: Spring Boot 4.0.0.
- Registry SSOT:
src/config/architecture/modules.json.
Package root: dev.caskeleton.bootstrap.
Responsibility
- Spring Boot entrypoint (
CaSkeletonApplication). - Runtime settings and logging bootstrap.
- Final cross-module wiring.
- Architecture tests that inspect all modules.
Allowed
- Runtime leaves explicitly declared by this module's Gradle dependencies and permitted by the architecture registry. The resolved Gradle runtime graph is the runtime SSOT; do not duplicate a membership list in metadata.
- Spring Boot startup/runtime dependencies.
- ArchUnit in tests.
Forbidden
- Concrete business policy.
- Controllers, use cases, repository adapters, or mappers authored directly under bootstrap.
- Settings classes that implement business logic.
- Implementing an
application-coreordomain-coreport. A class that implements one is an outbound adapter and belongs in anadapter/outbound/*leaf, however its dependencies are configured —CompositionRootBoundaryArchitectureTestenforces this, with no exceptions. - Raising a startup failure with
throw new IllegalStateException(...). UseStartupFailures(adapter:outbound:support, packagesupport.startup:envValidation/profileMismatch/requiredAdapterDisabled/migrationFailed), so the failure carries its sysexits exit code and structured log fields —StartupFailureContractArchitectureTestenforces this. - Answering "is this production?" locally.
dev.caskeleton.shared.runtime.RuntimeEnvironmentowns the profile vocabulary for the whole repository. - Depending on
org.testcontainersfromsrc/test. Real-service tests belong tosrc/integrationTest; seedocs/testing/TESTING_STRATEGY.md.
Package layout
The rules below exist because their absence is what produced the drift this module was reviewed for
(docs/reviews/2026-09-07-app-bootstrap-module-code-review.md, BOOT-006 / BOOT-007). Half the
capabilities lived under autoconfigure/ and half at the package root; Settings classes were split
between a settings/ package and their feature packages with no stated rule; and the same
decomposition problem was solved two different ways in the same leaf — Notification as nine focused
configurations, Redis as one 376-line class.
- A capability's assembly lives in the capability's own module, registered by that module's
AutoConfiguration.imports, with its settings in the module'sconfig/module-defaults/*.yml. JPA (startup guards, Flyway strategy, lock decorator, readiness and full-off handling inJpaActivationEnvironmentPostProcessor) isadapter:outbound:persistence-jpa; Redis (readiness) isadapter:outbound:cache-redis; notification iscomposition:notification-platform. Every capability is a commentedruntimeOnlyline inbuild.gradle; the default composition is web, observability, the cores, support and identifier. This leaf keeps no list of capabilities: no switch registry, no cross-capability dependency validator, no activation endpoint. Component scan coversdev.caskeleton.bootstraponly; web (WebAdapterAutoConfiguration,WebSecurityAutoConfiguration) and support (OutboundSupportConfig) arrive through their ownAutoConfiguration.imports. What stays inautoconfigure/<name>/is application composition over application-core ports that names no module type:operation(the durable operation use cases and their/operationsendpoints, on only when the operation store and the outbox append port exist),common. The outbox relay and the idempotency executor arecomposition:outbox-relayandcomposition:idempotency, selected by oneruntimeOnlyline each (the sample takes the idempotency one too). The runtime wiring both composition roots need — tracing, the metrics contract filters, domain-context propagation, user-principal pseudonymization (PrivacySettings) and the actuator chain — iscomposition:service-runtime, which the sample takes by the same line instead of carrying copies. <Capability>Settingslives beside its capability, not insettings/. Thesettings/package holds only settings that belong to no capability —BootstrapSettings,LoggingSettings,RuntimeSafetySettings.runtime/holds guards about the application itself — secrets, numeric bounds, error-detail exposure, multi-instance coordination, the runtime-profile check (RuntimeEnvironmentProfileValidator). A guard about a capability's settings (the JPA OSIV/DDL/pool/TLS/vendor guards, the Mongo connection-source rule, the GraphQL deployment-mode rule) ships with that capability's module, so it exists exactly when the capability does.- The startup failure vocabulary lives in
adapter:outbound:support(support.startup: phases, error codes, exceptions,StartupFailures,StartupValidationContext,StartupOrder,ReadinessGroup,RuntimeWarnings), so capability modules fail the same way without depending on this leaf.runtime/startup/keeps onlyStartupFailureExceptionReporter. - An environment-only guard is a
StartupRulebean (support.startup): it returns violations, and the oneStartupRuleRunnerraises them. A guard that needs another bean stays a bean. A capability's production secrets are the capability's: its module contributes aRequiredProductionSecretsbean, andSecretSourceValidatorchecks the names without knowing which roles exist.
Decomposition threshold
State it rather than leaving it to taste, because "it felt long enough" is what produced two different answers for the same question.
- One
@Configurationholds one assembly concern. Split when it passes roughly eight@Beanmethods, or as soon as it assembles two unrelated port families — whichever comes first. - One
@ConfigurationPropertiesclass owns one capability namespace. - A capability that needs more than one configuration gets a root class holding its
enabledcondition,@EnableConfigurationProperties, and an@Importof the per-concern classes. Scan nothing:@Importfrom a gated root is what keepsenabled=falseload-bearing rather than advisory.cache-redis'scapability/RedisCapabilityConfigis the reference example. Optional adapter capabilities that own reusable Spring composition publish their own root instead. Notification usesadapter:outbound:notification'sNotificationPlatformAutoConfigurationpluscomposition:notification-platform'sNotificationApplicationCompositionAutoConfiguration; JPA uses the package-privatePersistenceJpaAutoConfiguration,PersistenceJpaRuntimeConfigandstartup.JpaStartupAutoConfigurationfromadapter:outbound:persistence-jpa, which is not in the default composition (// runtimeOnly project(':adapter:outbound:persistence-jpa')inbuild.gradle). Mongo follows the same rule: the persistence-mongo leaf owns MongoRootAutoConfiguration and its internal health bridge; bootstrap owns no Mongo-specific production health configuration. - Shared helpers of a split capability get their own type named for what they are, not a
*Utilbucket —cache-redis'scapability/RedisKeysis the reference.
Test
cd src
./gradlew :app-bootstrap:test
./gradlew verifyCleanArchitectureDependencies