Ask HN: When do you start considering to 'separate' service designed with DDD
Hi, HN.
Recently, I've been obsessing about decoupling timing in DDD.
No matter how much I think about it, I feel like I won't find the answer till I actually go through it. So I'm looking for other perspectives.
If you are someone who maintains application designed with DDD, and traffic of one domain starts getting higher, when do you decide it's time to separate by control plane / data plane?
Do you treat this as an architectural concern from the beginning, or does it usually emerge later as the system grows?
I'm curious how people here make that call in real. I can’t answer this directly, but it may be helpful to others if they have an example (be it real or fabricated based on what you’re working with) to work from. Take a Notification domain — the template/rules/preferences side and the thing actually pushing millions of messages out the door have completely different needs. But I never know when to actually split them. Do you wait until the data plane's scaling starts making deploys painful? Or is there some earlier "oh this is getting weird" signal I should watch for?