[asim]

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 of those and that requires a single language and framework for it.

[kbutler]

> We think cloud is as complex Architecture as any of those and that requires a single language and framework for it.

Your conclusion does not follow from your premise.

[yowlingcat]

> We think cloud is as complex Architecture as any of those and that requires a single language and framework for it.

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?

[anamexis]

> all of frontend is JavaScript, iOS is objective C and Android is Java

To the extent that this is true, I don't think the complexity of the architecture has anything to do with the reason there's a single language for them.