I don't think "readiness" is something you completely do inside an app to begin with. (assist with? sure!)
This is why I proposed Condition Service; to model the details required for your application to be "ready", hoist that into an externally visible (to the java process) indicator (an open socket, REST endpoint, marker file) and THEN that can be used by any external readiness checker with whatever business logic. Apologies if my recommendation was unclear. But you're likely to have an orchestrator performing liveness/readiness checking anyway, why even try to model that entirely inside the application?!? - Ray
