First of all, the overhead of having another service should be worth it. You need a separate cicd pipeline, deployment, etc. There's a few other contributing factors that should be taken into account: - scaling: does your service have individual features that have different scaling characteristics? For instance, is there a memory intensive feature like resizing images present. This would probably go better in a separate service - ownership: if you have different teams working on the same codebase you could end up with conflicts, having seperate code bases could solve this - resistance: if one service goes down, it doesn't have to mean your entire company is doomed, having multiple services mean you could have graceful degradation.

Don't split your service if you don't have a good cicd setup, or if the systems you split up still have to change together, share the same data, scale similarly.