> 100 web applications in the world that need to be split into multiple services. Services are not micro services. Most large scale applications can and should

> 100 web applications in the world that need to be split into multiple services. Services are not micro services. Most large scale applications can and should be split into multiple services. However, when approaching a new problem you should work within the monolith resisting the service until you absolutely can't any longer. Ideally this will make your services true services, that could capture an entire business unit. When it's all said and done you should be able to sell off the service as a business. The other use case, which should be obvious, is compliance. If you are thinking about implementing anything that would require PCI or SOX you should do that in a service to shield the rest of the dev org from the complexities. So, any webapp that takes payment and interacts directly a payment processor. That said, you're correct in that you should not be rolling out a new service to avoid sharding.