anchor.diff:  
   NOTE: Dev Services for Elasticsearch is currently unable to start multiple clusters concurrently, so it only works with the default backend of the default persistence unit: named persistence units or named backends won't be able to take advantage of Dev Services for Elasticsearch.
   
  -For more information you can read the xref:elasticsearch-dev-services.adoc[Dev Services for Elasticsearch].
  +For more information you can read the xref:elasticsearch-dev-services.adoc[Dev Services for Elasticsearch guide].
   
   == Creating a frontend
   
  
positive.code: Quarkus supports a feature called Dev Services that allows you to start various containers without any config.
  In the case of Elasticsearch this support extends to the default Elasticsearch connection.
  What that means practically, is that if you have not configured `quarkus.hibernate-search-orm.elasticsearch.hosts` Quarkus will automatically
  start an Elasticsearch container when running tests or dev mode, and automatically configure the connection.
  
  When running the production version of the application, the Elasticsearch connection needs to be configured as normal,
  so if you want to include a production database config in your `application.properties` and continue to use Dev Services
  
negative.code: quarkus.hibernate-search-orm.elasticsearch.analysis.configurer=bean:myAnalysisConfigurer <6>
  quarkus.hibernate-search-orm.schema-management.strategy=drop-and-create <7>
  quarkus.hibernate-search-orm.automatic-indexing.synchronization.strategy=sync <8>
  
  %prod.quarkus.datasource.jdbc.url=jdbc:postgresql://localhost/quarkus_test <9>
  %prod.quarkus.datasource.username=quarkus_test
  %prod.quarkus.datasource.password=quarkus_test
  %prod.hibernate-search-orm.elasticsearch.hosts=localhost:9200 <9>
  ----
  <1> We won't use SSL so we disable it to have a more compact native executable.
  <2> Let's create a PostgreSQL datasource.
  