Microservices are good when one programming language is better at solving something than another. Eg. Python is what data scientists use for machine learning, b

Microservices are good when one programming language is better at solving something than another. Eg. Python is what data scientists use for machine learning, but I'm not going to build the entire backend in Python just because of that. C# is great for gluing things together and integrating with enterprise systems due to good support for wsdl, and the type system and tooling is excellent, as well as the pool of developers proficient in the language. Postgres/SQL is excellent for business logic, and can act as a kind of monolith. Other languages such as Go are great for a custom reverse proxy when Nginx is insufficient. And having the services seperated means one can crash without affecting the others (Erlang got this right, but I wouldn't build 100% of a system in that because of the reasons just mentioned). I like how microservices allow me to use the right tool for the job.