anchor.diff:  All that is needed to enable the fault tolerance features in Quarkus is:
   
   * adding the `smallrye-fault-tolerance` Quarkus extension to your project using the `quarkus-maven-plugin`:
  -
  -  `mvn quarkus:add-extension -Dextensions="smallrye-fault-tolerance"`
  -
  ++
  +[source,shell]
  +----
  +mvn quarkus:add-extension -Dextensions="smallrye-fault-tolerance"
  +----
   * or simply adding the following Maven dependency:
  -
  -  [source,xml]
  -  ----
  -    <dependency>
  -      <groupId>io.quarkus</groupId>
  -      <artifactId>quarkus-smallrye-fault-tolerance</artifactId>
  -    </dependency>
  -  ----
  ++
  +[source,xml]
  +----
  +<dependency>
  +    <groupId>io.quarkus</groupId>
  +    <artifactId>quarkus-smallrye-fault-tolerance</artifactId>
  +</dependency>
  +----
  
positive.code: 
  Check the server output to see that fallback is really happening:
  
  ```
  2019-03-06 13:21:54,170 INFO  [org.acm.fau.CoffeeResource] (pool-15-thread-3) CoffeeResource#recommendations() invocation #2 returning successfully
  2019-03-06 13:21:55,159 ERROR [org.acm.fau.CoffeeResource] (pool-15-thread-4) CoffeeResource#recommendations() invocation #3 timed out after 248 ms
  2019-03-06 13:21:55,161 INFO  [org.acm.fau.CoffeeResource] (HystrixTimer-1) Falling back to RecommendationResource#fallbackRecommendations()
  ```
  
  NOTE: The fallback method is required to have the same parameters as the original method.
  
  
negative.code: 
  Why not check that our application works? Run the Quarkus development server with:
  
  [source,shell]
  ----
  mvn compile quarkus:dev
  ----
  
  and open `http://localhost:8080/coffee` in your browser. Make couple of requests (remember, some of them we expect
  to fail). At least some of the requests should show us the list of our coffee samples in JSON, the rest will fail
  