Spring Boot or Ktor
Latest stable Based on Leader release 0.4.0
Choose integration from the host framework’s lifecycle and invocation model, not feature count.
Spring Boot
Section titled “Spring Boot”Use the Spring module when electors should be auto-configured and methods guarded declaratively with @LeaderElection or @LeaderGroupElection. Release 0.4.0 uses AspectJ compile-time weaving, not proxy-only interception. It supports synchronous, suspend, Mono, Flux, and Flow shapes with stream-specific lease rules.
Use the Ktor plugin when the service already owns coroutine scheduling and wants an application-scoped SuspendLeaderElector. leaderScheduled() binds the periodic job to Ktor lifecycle and cancels it on ApplicationStopped.
Boundary
Section titled “Boundary”Neither integration turns leader election into a scheduler or durable queue. Spring’s annotation wraps an invocation; Ktor’s helper launches a periodic coroutine. Misfire recovery, durable work state, retries, and idempotency still belong to the application or a job framework.
Release sources
Section titled “Release sources”leader-spring-boot/README.mdleader-ktor/README.mdexamples/ktor-app/src/main/kotlin/io/bluetape4k/leader/examples/ktor/KtorAppMain.kt