Teams have a lot to do with microservice use. If you have a small team a monolith can work well. If you have a large team, microservices have some significant a

Teams have a lot to do with microservice use. If you have a small team a monolith can work well. If you have a large team, microservices have some significant advantages. And in some cases, you might have a microservice in Swift when you need high performance, but other less intensive services might be in Ruby or some other language, etc. Right took for the job should be the goal as opposed to chasing fashion. Microservices are definitely overused, but they do have many legitimate use cases. Your CRUD web application probably doesn’t need microservices, but complex build systems might. Imagine the complexity of Amazon.com or Netflix were a monolith. But something like Basecamp is probably better as a monolith. There is also the issue of scale. An ML processor might need more (and different) hardware than a user with system. Right tool (and architecture) for the job.