Skip to content

Coupling Inventory ​

The scan counted source matches in main framework and plugin source, excluding target/, .git/, and IDE files.

CategoryCurrent countMain hotspotsMigration difficulty
Quarkus-specific runtime APIs134 matches in 42 runtime filesPipelineStepResolver, config classes, gRPC customizers, context filters, ItemRejectRouterMedium
Quarkus deployment APIs198 matches in 37 deployment filesOperatorInvokerBuildSteps, StepClientRegistrar, StepServerRegistrar, PipelineFrameworkProcessorHigh but isolated
CDI/Jakarta DI and lifecycle343 matches in 72 runtime filesPipelineExecutionService, QueueAsyncCoordinator, AwaitCoordinator, CheckpointPublicationService, PipelineRunnerMedium
Mutiny1,347 matches in 111 runtime filesPipelineStepExecutor, QueueAsyncCoordinator, AwaitStepSupport, PipelineExecutionService, AwaitCoordinatorHigh if removed, medium if adapted
Panache/Hibernate Reactive0 matches in framework runtime, 8 matches in 2 persistence plugin filesReactivePanachePersistenceProvider, PersistenceServiceLow to medium
Vert.x33 matches in 8 runtime files, 27 matches in 3 persistence plugin files, 22 matches in 4 deployment filescontext holders, persistence context safety, renderer annotationsMedium

The runtime module POM is a larger blocker than many individual classes. framework/runtime/pom.xml currently pulls Quarkus config YAML, context propagation, Picocli, gRPC, cache, REST, REST client, Micrometer, OpenTelemetry, SmallRye health, DynamoDB, and SQS dependencies. A neutral runtime-core artifact cannot carry this dependency shape.