IMO you should never create a new service unless it serves an engineer reason instead of an organizational one. There's a lot of tools to help out monoliths, an

IMO you should never create a new service unless it serves an engineer reason instead of an organizational one. There's a lot of tools to help out monoliths, and a lot of ways to make it easier to shard the monolith as well. Some services need it, like a backend intake platform of some sort that needs to have radically different performance characteristics than a user facing frontend. But for most services it just does not make a lot of sense to do this.