I'm partial to Compojure API (https://github.com/metosin/compojure-api https://github.com/metosin/compojure-api). The thing I like about it, is at the point whe

I'm partial to Compojure API (https://github.com/metosin/compojure-api https://github.com/metosin/compojure-api). The thing I like about it, is at the point where I've just scaffolded a barely functional prototype, I also have a spec and interactive documentation. That documentation serves as the service's first UI. UX peeps think I am sadistic, but I like having the controls embedded in the manual. It is also very beautiful. If you look at the examples, there are few forms (keywords, in other languages) that are not related to the domain of an HTTP API. The code is dense, but rich in relevant information. If you want to explore the underlying architecture, look up the Ring project. It contains the lower level server primitives that several web frameworks are built on top of.