This ties to the lazy database discovery in Cloud environments. The
issue related to that also mentions a health check API.
I don't think it ties to the Stats or JMX API as at least for the
initial start, this API should be able to provide feedback while
Hibernate engine is starting (and looping).
It would be interesting to explore what other IO engines offer as health
check APIs to be inspired (straight poll, callback etc).
Emmanuel
On Thu 18-05-31 17:40, Sanne Grinovero wrote:
It was suggested to me that Hibernate ORM could help people
developing
microservices on Kubernetes / Openshift by making "health checks"
easier.
In short, how to expose to some management API that we're being able
to connect to the database and do our usual things.
This could be done by connection pools as well but I suspect there
could be benefits in exposing this information in a unified way at an
higher level API; also on top of using ad-hoc specific connection
APIs, or Dialect specific instructions, I guess we could monitor
timeout exceptions, etc.. happening on the application sessions.
Wrote some notes on:
-
https://hibernate.atlassian.net/browse/HHH-12655
Probably best to explore this in ORM first, but then Search and OGM
could expose/implement it too for their respective services?
Or maybe people would prefer to just run a query?
Thanks,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev