anchor.diff:  ----
   
   Taking this simple GET operation, we can use Quarkus to build a runnable jar or even a native image which we can then embed in a Docker
  -image or for use in a Knative Build script for deployment on top of kubernetes.
  +image or for use in a Knative Build script for deployment on top of Kubernetes.
   
   [source, shell]
   ----
  
positive.code:     @Inject
      EntityManager em;
  
      @Inject
      UserTransaction transaction;
  
      @GET
      @Produces(MediaType.TEXT_PLAIN)
      @Transactional
  
negative.code: mvn quarkus:native-image ## produces a standalone executable
  ----
  
  The runnable jar can then be executed simply by running `java -jar target/myapplication-runner.jar`.
   The native image can be run with `target/myappliction-runner`.
  Either scenario requires minimal work, then, to bundle in to your preferred FaaS platform.
  
  === FaaS API
  All this begs the question: why doesn't Quarkus simply provide its own opinionated API?  While this may happen eventually, the current
  