Well, not much of a comparison here, though one observation: I wouldn’t say that Gin’s logging implementation is superior in any way. For most intents and purposes, modern containerised services would do well to be able to output JSON logs. In Gin it’s easy to add a JSOn logging middleware that overrides the build in key/value one but to convert all of the frameworks logs to JSON is unnecessarily complicated. Also, their own logger wraps Logrus, which is the slowest of the Go logging tools (particularly with JSON).

Echo does a much better job at it, not to mention it logs natively to JSON (but it’s trivial to switch to a key/value log).


Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store