anchor.diff:  java -Dcatacumba.port=8000 -Dcatacumba.debug=false -jar yourjarhere.jar
   ----
   
  +
   == Examples
   
   
  
positive.code: 
  == FAQ
  
  TBD
  
  
  == Developers Guide
  
negative.code: 
  * The pedestal approach is very opinionated and too much high level and I prefer something simple
    and lightweight.
  * Aleph, seems a great library but lacks of good, readable, user friendly documentation a
    nd its generic approach (not only http) not helps much. If you want read more about differences with
    aleph, see <<difference-with-aleph,this>> faq entry.
  * Jet is a asynchronous ring addapter for jetty9. It is really great library that I have used in
    some projects, and fits very well on my idea of web toolkit but it has two drawbacks, it is build
    as ring adapter having all the good and all the bad of ring and it is using jetty (jetty is a
    servlet server that comes with optional async support, it isn't asynchronous from the ground up).
  
  === Goals
  
  Here a incomplete list of things that _Catacumba_ goals:
  
  * Have a flexible and extensible way to setup different kind of handlers
  * Provide a simple and lightweight approach for define asynchronous web services with support for
    different abstractions, such as promise, future, core.async, manifold, reactive-streams, ...
  * Build almost everything up on abstractions for simple and easy extensibility.
  * Provide a builtin, data based routing.
  * To be flexible and not very opinionated.
  * Have backpressure support out of the box.
  
  _Catacumba_ goals are not:
  
  