Well... don't do that? This is where microservices comes in. In a SOA architecture nothing really tells you when it's a good idea to split things up. Microservices is a methodology to help you avoid this exact situation.
You'd have the same problem in a monolith if you have two different modules working on the same db.
