I'd say so. What we did is if you make a description of what a service does like "this service ingests data X and stores it in a database and makes it available

I'd say so. What we did is if you make a description of what a service does like "this service ingests data X and stores it in a database and makes it available as an API and aggregates it into business events and makes predictions based on it" we cut the services on the and's. This example now is 3 services: DB + API, event generator and predictor. I'm still glad we let it evolve that way instead of starting out separately.