Hi Sanne, whatever you consider to implement in Hibernate ORM/Search/OMG I think you should use/follow the MicroProfile Health spec [1]. As far as I know WildFly Swarm supports already this spec.
Best regards, Andrej Golovnin [1] https://github.com/eclipse/microprofile-health/ > On 31. May 2018, at 18:40, Sanne Grinovero <sa...@hibernate.org> 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@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
