anchor.diff:  
   == SparkJava
   
  -Don't confuse Spark with Apache Spark. It has nothing in common. Spark is a tiny Sinatra inspired framework for creating web applications in Java 8 with minimal effort. In effect it is tiny, but very feature rich.
  +Don't confuse Spark with Apache Spark. It has nothing in common. "`Spark is a tiny Sinatra inspired framework for creating web applications in Java 8 with minimal effort`". Indeed it is tiny, but very feature rich.
   
   === Main
  +The main method is pretty much like other frameworks main: plumbing to wire routes. Note that Spark doesn't use Jackson as mapper, but optionally uses a mapper passed as parameter of some route configuration calls. A mapper is simply a method taking an object as parameter and returning a String.
  +
  +All configuration is done calling static methods on the Spark class.
   
   === Resources
   
  
positive.code: router.route("/*").handler(auth);
  ----
  
  === Monitoring
  
  Vertx offers a metrics system, with many different metrics. Of course, you can register your own metrics using the MetricsRegistry.
  
  === Conclusion
  
  Vertx is really complete. It is built on top of Netty, and offers a performant system. As it is written in Java 8, you can write TODO
  
  TODO...
  As Vertx is asynchronous by nature, you can feel it puzzling at first sight for people like me that are not used to this programming style. But once you get the thing, it's probably one of the best tools I ever used.
  
  == Spring Boot
  
  
negative.code: 
  * I'm about to build a tiny RESTful API. UI is not considered in this article (note that every candidate framework has a mean to serve static resources easily)
  * Only use HTTPS to access the API
  * The API will have two sets of resources (aka two microservices): a simple hello world resource calling a cars resource to get cars available (what a useless example!). For simplicity's sake, they will be deployed in the same server, but will communicate over HTTPS.
  * The resource will have a JSON representation
  * Each representation will have at least a self link to the resource
  * After a resource creation, client receive a Location header (the resource's link)
  * The API will be accessible only by people providing a Facebook OAuth token
  * Each API must have a monitoring / metrics facility (not tested though)
  * Each service may be packaged as a standalone jar, to be run using `java -jar`.
  
  == The candidates
  
  