If you split a monolith while both services still write the same tables, you get a distributed monolith with extra latency. We draw the boundary at data ownership rather than deployment units, so the question we start with is who owns the write path for each table.
Was this useful?