Our great sponsors
-
gofre
A fast and low memory consumption web framework for Go with middleware support and without third-party dependencies
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Hi sikoyo, and thanks for your appreciation. If it will be to compare with other popular frameworks, not only with Echo, it will be like: 1. The programming model is simple and natural. For example a GoFre handler returns a response or an error. The response is an interface with 4 methods, compared with Echo which provides a Context (an interface with 55 methods :) ). Imagine if you want to extend Echo with response compression how simple it is? In GoFre just implement a new Response that wraps the original response. See this implementation https://github.com/ixtendio/gofre/blob/main/response/compress.go for example Gin, another framework uses the same concept like Echo :) but at least in their case the Context is not an interface but a structure which contains a lot of fields which should not be there. The same problem here, how easy is it to extend it for your needs? 2. Another difference is in patch matching. GoFre supports approximately the same path matching as the Java Spring framework. For example if you have the following patterns: