@olanod that's a good question that I'm asking myself too. What I do is make sure to separate the parts of my API which need to be blazing fast, and those which can be a bit slower or are more tied into other parts of the infrastructure. In my case, our API currently runs on Django (Python). It works great when we have to get a ton of stuff from the database or from other external sources. However, we also have two main endpoints which need to be blazing fast and whose return value is not used on the client side (unless an error code is returned). These are the ones we are porting to gin, mainly because we can make use of channels in go to deliver incredible speed on these endpoints.