Micro services is apparently a new buzzword in software engineering world, despite of the fact that it is essentially just another term for something known as SOA for many years (yes, I know that there is some difference in perception of these two terms, but underlying idea has not changed). Attention to such architecture was heated by example of large internet companies like Netflix and Amazon. Some companies publish code of infrastructure components as open source.
Though micro services architecture is more suitable for polyglot technology than monolithic, language and platform still matters. It might be beneficial to use the same infrastructure for all micro services, to reuse deployment, messaging, logging and monitoring components. It is even better if some of these components can be available for free as open source libraries.
Now if you are Java developer, you have huge advantage, because so many large companies use it. If you search for “Java micro services” you will find hundreds of articles and presentations, libraries as Finagle by Twitter, Hystrix by Netflix, even meetup events.
Is it because .NET is mostly for enterprise solutions and enterprise developers have not yet adopted micro services? Or just because Microsoft licensing is not working well with scale-out approach of service-oriented architectures?