This is all fine and dandy until you add persistence / need microservices talk to each other, follow requests through the entire flow etc.
Just think about user creation. After a user is created, a common thing is to send a welcome email. Then you probably need to build an email service because you probably want to mail other times as well.
But if an email fails to be sent because there is an error in the service, you need to build around that and report it somewhere. You would probably make some kind of class or library that makes these requests to other microservices and now you're already on a path to hell because then that library is in language x and cannot easily be ported to another service etc.
Polyglot microservices is a shitty idea. It makes a hell for developers, a hell for maintenance and it doesn't give the end user any more value.
I am not really a fan of microservices as a concept in general, but polyglot microservices, seriously who would want to do that?
Just think about user creation. After a user is created, a common thing is to send a welcome email. Then you probably need to build an email service because you probably want to mail other times as well.
But if an email fails to be sent because there is an error in the service, you need to build around that and report it somewhere. You would probably make some kind of class or library that makes these requests to other microservices and now you're already on a path to hell because then that library is in language x and cannot easily be ported to another service etc.
Polyglot microservices is a shitty idea. It makes a hell for developers, a hell for maintenance and it doesn't give the end user any more value.
I am not really a fan of microservices as a concept in general, but polyglot microservices, seriously who would want to do that?