From Red Hat
He had founded and lead Hibernate Search, Validator and OGM and participated to the Bean Validation spec (as lead) and the JPA one (as expert).
Nowadays his focus revolves around NoSQL, analytics and streams of data.
Rich UIs, schemaless datastores, microservices communicating with each other - the need for powerful and easy-to-use data validation services has never been bigger: guard your services endpoints, your datastore accesses against garbage is important in an analytics shifting universe.
The Bean Validation standard is here to help, providing Java developers with a rich validation API based on annotations. Bean Validation 2.0 (JSR 380) takes validation to the next level by leveraging Java 8 features such as lambdas, additional annotation locations and repeatable annotations. This opens up exciting opportunities for Bean Validation - e.g. List<@Email String>. There will also be support for
java.time API and more. Join us and see what's planned for Bean Validation 2.0 and what's already done. Like its predecessors, JSR 380 is developed fully in the open: come exchange, propose and participate!
Elasticsearch is a highly scalable search engine and simple to deploy.
One of the challenges is to keep the data source (e.g. RDBMS) and the Elasticsearch index synchronized all the time. And yes it is more complicated than you think.
Hibernate ORM is very popular to persist data in RDBMSes from Java.
Wouldn’t it be good if Hibernate ORM could automatically push all changes to Elasticsearch? Wouldn’t it be good if Elasticsearch queries could return domain model objects like a HQL query?
Please welcome the latest feature of Hibernate Search, come discover via this tools in action how the Elasticsearch and Hibernate universes are joined and why such combination is so useful.