Echo wrapper

[AdrianCio]

Hey!
At IKEA we build many microservices and we use echo as the framework of choice. Over the years we realized we write a lot of boilerplate around enhancing our services (logging, tracing, API routing logic, etc.) and we started playing with the idea of reducing this boilerplate by writing a wrapper on top of echo. Our goal was to allow users to define their service via a simple config so that they could in the end run something like fastecho.Run(config). The whole setup is behind the reusable library we built which helps with maintenance. This also makes creating new microservices incredibly easy because developers can focus on the actual functionality of the API since the service logic just works.

We are now exploring the possibility of opensourcing this library we created because we believe this will be helpful for others as well to have a prepackaged microservice solution based on echo. As part of this process we wondered whether this approach is in alignment with Echo's vision and goals and whether this can or should become part of the Echo repository itself or whether we should publish it as a 3rd party.

[aldas]

Sorry for the late reply. It is a cool idea.

Please release it under you company account. Echo has policy to avoid adding 3rd party libraries as dependencies in Core (it becomes maintenance nightmare). Also if it is under your control you have freedom for changing directions, release cycle etc.