advancedProduction Best Practices

Why does a service need graceful shutdown configured, not just a health check?

Without it, Kubernetes' termination signal during a routine deployment hard-kills in-flight requests instead of letting them finish, producing user-visible errors on every single deployment — `server.shutdown=graceful` stops accepting new requests immediately while letting existing ones complete within a timeout.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

Why does a service need graceful shutdown configured, not just a health check?

Next Step

Continue to Why should environment-specific behavior live in profile-specific properties files instead of if-checks in code?← Back to all Spring Boot questions