http-cache VS handlers

Caching Middleware victorspringer/http-cache

When you use a router that supports http.Handler you don't have to worry about maintaining special middleware for that library. There are so many well maintained middleware libraries for the http.Handler like https://github.com/gorilla/handlers

To add to this, gorilla also offers some middleware. And its super easy to import your own and wrap it.

Study the generic reader/writer implementations in the io module. (On my system, those sources are in /usr/lib/go/src/io.) The io.Reader and io.Writer interfaces are very simple, but very powerful because of how they allow composition. A shell pipeline like `cat somefile.dat | base64 -d | gzip -d | jq .` can be quite directly translated into chained io.Readers and io.Writers.

Another example of this is how HTTP middlewares chain together, see for example all the middlewares in https://github.com/gorilla/handlers. All of these exhibit one particular quality of idiomatic Go code: a preference for composition over inheritance.

Another quality of idiomatic Go code is that concurrent algorithms prefer channels over locking mechanisms (unless the performance penalty of using channels is too severe). I don't have immediate examples coming to mind on this one though, since the use of channels and mutexes tends to be quite intertwined with the algorithm in question.

gorilla/handlers