Yeah, Having built a web application serving 100K+ users in Go. First 2/3 weeks were spent on making sure we were a framework. So new Modules could be added. New external calls were abstracted and also dealt with lot of circular dependency.

This was all fun and learning, but wouldn't mind having a "Flask" or "Express" version of a Golang framework which took care of all the boilerplate out of the box.

We did try some existing solution to no avail like Tiny etc.

But ended up building a non-framework framework anyways especially to support new features/modules and new devs coming it.