anchor.diff:  |**Heavyweight Runtime**
   |Typical use while coding
   
  -- Single-thread HTTP stack `1*acceptors`+`1*acceptors`
  +- Single-thread HTTP stack `1 * acceptor-thread` + `1 * io-thread`
   - Reload on source changes
   - Stacktraces disclosed in responses
   |For tests that require a complete HTTP stack
   
  -- Single-thread HTTP stack `1*acceptors`+`1*acceptors`
  +- Single-thread HTTP stack `1 * acceptor-thread` + `1 * io-thread`
   - Compiled bytecode execution
   |Typical production model
   
  -- Multi-thread HTTP stack `cores*acceptors`+`cores*io`
  +- Multi-thread HTTP stack `cores * acceptor-threads` + `cores * io-threads`
   - Compiled bytecode execution
   
   |**Middleweight Runtime**
  
positive.code: 
  . **Heavyweight**, with HTTP Service, most used runtime model for a HTTP application.
  . **Middleweight**, with HTTP Context but without HTTP Service, typical runtime model for controller tests.
  . **Lightweight**, with **no** HTTP support, usefull for applying the worker runtime model easily ; that is execute some
  application code in a lightweight process.
  
  TIP: See the Deploy on Heroku guide for lightweight mode usage example implementing Heroku workers.
  
negative.code: - Netty
      - Netty Selector Threads, default to `Runtime.availableProcessors()`
       -Netty IO Threads, default to `Runtime.availableProcessors()`
  - Application
      - Application Execution Thread Pool
      - It means that by default, none of your controller code is executed on the IO Threads and that any controller doing
        blocking operations will not slow your application down.
  
  
  === Summary
  