Earlier quoted context omitted.
Heroku for sure. It’s all running on AWS so you can leverage AWS services without as much of a performance penalty for routing as say another provider. I don’t understand how this Micro framework is valuable unless your entire team writes Go. Even then, this is not just ‘micro services’ it’s a monolith on a proprietary framework that happens to have network hops between function calls. It is the kitchen sink!
All your services are written independently as microservices. In fact Micro is itself a microservices architecture and each feature is an independent service backed by highly available managed infrastructure. Yes we expect you to write everything in Go. I don't think that should be surprising since all of frontend is JavaScript, iOS is objective C and Android is Java. We think cloud is as complex Architecture as any…
I think this is a spectacular claim that requires spectacular evidence. Service code is a different beast from interface code. The most practical reason to use the microservices pattern is to enable polyglot programming so you can use the right ecosystem for the right job. Need a monolith API gateway wrapper to throw up a CRUD app real quick? Ruby and Python have got you covered. Need access to a large enterprise system? Great, you've got Java and .NET. Inheriting a crufty legacy WordPress codebase and need to make it better without a full rewrite? PHP has ways to make it less shitty.
Could you give me a compelling reason why I, if I had a codebase already written on any of those languages, would entertain rewriting the whole thing in Go to use your framework? Would theoretical me not be in your target user demographic?