Each services need to communicate with each other. And, 100 things can go wrong in that and lot of effort and fail-safe mechanisms has to be put in order for it to scale. Having said that there are lots of solutions out there but does require good amount of understanding and work
https://phil.us - Phil is a San Francisco-based health-tech startup with the mission of reinventing the $400B prescription medication space. In the last 18 months we went from prototype to figuring out product-market fit, to establishing our high-margin unit economics and raising over $12M in two rounds of venture financing. Our asset-light business model has helped us expand from the state of CA to cover 92% of US population in the last six months. Now looking to grow our small and close-knit team in sunny downtown SF.
First question I would ask is do you really need a web framework? With Go, the way language is built or designed - you don't need crazy frameworks. Having said that I do use gorilla package a lot to re-use some of the common middlewares and packages which wouldn't make sense to re-write. But, for API endpoints and all that I am directly using Go.
You don't need crazy frameworks in any language. However I think about the things different frameworks give me. Generation of database migrations and other standard elements, an ORM and/or query DSL so my SQL code can be more DRY, a community with a shared code base so that I don't have to rediscover every solution or rewrite everything for my particular use case, and additional domain knowledge that is transferable to other projects/companies so that I can be immediately productive.
I mean I like Go, and I understand that layer of abstraction can be frustrating, especially in a typed language, but that layer of abstraction can also be incredibly useful.
