Loading
Pick a focused question that fits your time, stack, and interview goal.
24 results across 1 active filter
Page 1 of 1
Coordinates readiness, server draining, lifecycle timeouts, background work, and platform termination during a Spring Boot shutdown.
Explains one observation lifecycle feeding metrics, tracing, and context through registered handlers.
Explains cache interception, keys, conditions, eviction, proxy self-invocation, and the provider boundary.
Builds stable Micrometer dimensions that answer operational questions without unbounded time series and cost.
Propagates trace and observation context through supported clients and executor boundaries without passing framework state manually.
Separates restart-worthy process failure from traffic readiness and composes Spring Boot health groups around those meanings.
Builds outbound resilience from deadlines and operation safety, then adds bounded retry, circuit, and concurrency controls with telemetry.
Creates queryable structured events with trace correlation, stable fields, useful context, and deliberate redaction.
Moves from user-visible latency to route, dependency, database, executor, JVM, and change evidence before selecting a fix.
Uses Hikari metrics, thread evidence, database activity, transaction scope, and query behavior to separate leaks from slow or excessive work.
Separates server request capacity from application executor capacity and finds blocking, queueing, rejection, or downstream causes.
Keeps cached reads acceptably fresh and prevents hot-key reloads from overwhelming the database across application instances.
Coordinates startup work, readiness, schema compatibility, warmup, and mixed-version traffic during a rolling release.
Binds typed configuration, understands property precedence, validates startup invariants, and keeps secrets outside source control.
Reviews correctness, boundaries, failure behavior, capacity, security, observability, delivery, and recovery through concrete evidence.
Sizes per-instance database concurrency from workload and database capacity instead of equating more connections with more throughput.
Uses thread dumps, heap dumps, logger changes, mappings, and configuration evidence through a tightly controlled operator path.
Uses Actuator for operational visibility while controlling endpoint exposure, access, detail, and network reachability.
Designs scheduled work for overlap, multiple replicas, restart, failure, and durable ownership instead of assuming one execution.
Separates transaction-phase callbacks inside one process from durable database-backed publication across process failure.
Combines Spring Boot signals into an operator-focused baseline for service health, dependencies, capacity, releases, and actionable alerts.
Treats @Async as an in-process executor boundary with proxy, failure, context, capacity, and durability consequences.
Separates in-process decoupling from durable cross-process delivery and makes timing, failure, and transaction expectations explicit.
Adds dependency health only when it supports a specific operational decision and can be checked cheaply and safely.