anchor.diff:  
   ### Microservice 101
   
  -_Microservice_ is an _architectural style_, which means it is a _specialization of element and relation types, together with
  +_Microservices_ is an _architectural style_, which means it is a _specialization of element and relation types, together with
   constraints and how they can be used_ footnote:[This is the definition of _architecture styles_ from the Software
  -Engineering Institute.]. I believe by now, I have left you more confused than you before we started.
  +Engineering Institute.]. I believe by now, I have left you more confused than you were before we started.
   
   Not to worry. Let's take another approach. Why do we need _microservices_? In one word: **agility**
   footnote:[Ability to move quickly and easily, not related to the Agile methodologies]. Let's imagine, we have
  -an  application, rather large. As a large application, the maintenance is a nightmare, adding features take
  +a rather large application. As a large application, the maintenance is a nightmare, adding features takes
    too much time, the technology used is very outdated (What? Corba is not cool anymore?), any change needs to pass a
  - 50-steps process and be validated by 5 levels of management. Obviously there are several teams on the application with
  + 50-steps process and be validated by 5 levels of management, the list goes on. Obviously there are several teams on the application with
     different requirements and agendas. Well, we have such a _monster app_. How could we make the development and
     maintenance of this application efficient? Microservices are one answer to this question. It aims to reduce the
     _time to production_.
  
positive.code: 
  ### Exercise 3 - Consuming a service using sugars
  
  This exercise is equivalent to the previous one, but use the higher-level API. Use the method `io.vertx.reactivex.servicediscovery.types.HttpEndpoint#rxGetWebClient` to retrieve a `WebClient` directly.
  
  [.assignment]
  ****
  
negative.code: ### Time to go further
  
  Microservices are a great way to improve the _agility_ of your product. But, it introduces a lot of moving parts, and
   keeping everything on track is not a simple task. Service discovery lets the different parts discover one another and
    interact, but what about deployment, monitoring, and other administration tasks? For these, we will look into
    containers and Kubernetes in the next chapter.
  
  