Absolutely I would. Everyone has their opinion about Microsofts products, but the platform and frameworks that underpin them are rock solid, long-time battle-tested in production, and easy to work with as a developer.
A .net stack comes with the comforting knowledge that this technology will never be made obsolete. It will undergo active development and will have support for many years to come. One day, long into the future, it will be super seeded by something else. When that happens, you know there will be a migration path because Microsoft has based their own business on it, and they need it for themselves, and all of their customers need it. .net does not go away tomorrow because something shinier showed up.
That's nice to know.
You will find that you will have a very stable and mature stack that is well integrated with Azure making deployment and testing easy.
Was I to build a microservice application, I would not choose Kubernetes.
I would choose the Microsoft Service Fabric Actor model over anything else that is out there.
Service Fabric is Microsoft Secret Sause. It is the technology that underpins the Azure Platform itself. Service Fabric has a beautiful actor model that makes the development of cloud-based applications as simple as writing a single threaded console application.
Service Fabric and Kubernetes: community comparison [1]
The Actor Model [2]
[1] https://docs.microsoft.com/en-us/archive/blogs/azuredev/serv...
[2] https://www.youtube.com/watch?v=7erJ1DV_Tlo
