Extend & integrate
Hook into the task lifecycle, watch what it does, and wire the Java SDK into the rest of your stack.
Hook into the task lifecycle, watch what it does, and wire the Java SDK into the rest of your stack.
Everything that attaches to flexiq from the outside: the extension points that run inside the task lifecycle, the signals they emit, and the frameworks and vendors on the other end of those signals.
Lifecycle events and middleware are the extension points for pushing any of these signals to an external system.
See what the queue is doing — counts, per-execution metrics, live workers,
per-job logs — and emit structured logs, all from the FlexiQ handle with no
extra service.
The Java SDK ships a Spring Boot 3 starter as a separate artifact, and two
observability helpers in the org.byteveda.flexiq.contrib package of the main
artifact. The contrib classes compile against their third-party APIs as
compileOnly dependencies — nothing is pulled onto your classpath until you
add the matching runtime dependency yourself.
// Only add what you use.
implementation("org.byteveda:flexiq-spring:1.0.0") // Spring Boot 3 starter
implementation("io.micrometer:micrometer-observation:1.13.6") // contrib.FlexiQObservation
implementation("io.sentry:sentry:7.14.0") // contrib.SentryMiddlewareIntegrations never auto-initialize. Nothing runs until you construct the
class and register it with flexiq.use(...) (or, for Spring, until the
starter is on the classpath). If the runtime dependency is missing, using the
contrib class fails with a standard NoClassDefFoundError.