anchor.diff:  }
   ----
   
  -But you may be wondering where is configured the URL as it's not in the code.
  -Remember, it must not be in the code, because the url is likely depending on the environment.
  +But you may be wondering where the URL is configured as it's not in the code.
  +Remember, it must not be in the code, because the url likely depends on the environment.
   The URL is configured in the application configuration:
   
   [source, text]
  
positive.code: Finally, methods requiring running in a transaction are simply annotated with `@Transactional`.
  
  Let's now imagine you need to access another HTTP endpoint.
  You can use a HTTP client directly, but, it's often a boring task and the code can become quickly repetitive.
  Quarkus provides a way to call HTTP endpoint easily.
  
  First declare your service as follows:
  
negative.code: 
  == Being reactive
  
  Application requirements have changed drastically over the last few years.
  For any application to succeed in the era of cloud computing, big data or IoT, going reactive is increasingly becoming the architecture style to follow.
  
  Today’s users embrace applications that have milliseconds of response time, 100% uptime, lower latency, push data instead of pull, higher throughput and elasticity.
  