3 ms·
Gin and Echo cover similar feature scopes (the HTTP plumbing around your business logic, that you write in handler functions), but I chose Echo for my project[1
by xvello 4y ago
Gin and Echo cover similar feature scopes (the HTTP plumbing around your business logic, that you write in handler functions), but I chose Echo for my project[1] because:
- it ships a pretty extensive collection of middlewares that will get you to 80% faster
- the documentation[2] is really well written and accessible to new web developers: most "must have" features have a cookbook page, so you don't have to google for blog posts.
- it does indeed use a custom handler function signature, but in my opinion this one is better (returning errors instead of handling them locally in each handler). You can still use handlers and middlewares written for other frameworks (for example the great statigz[3] handler) through the `echo.WrapHandler` and `echo.WrapMiddleware` functions
[1] https://github.com/letsblockit/letsblockit https://github.com/letsblockit/letsblockit
[2] https://echo.labstack.com/guide https://echo.labstack.com/guide
[3] https://github.com/vearutop/statigz https://github.com/vearutop/statigz
- molly0 4y agoThank you for this answer, it’s great to get tips like this when starting with a new language.