That's a good point about the context, but not very concrete.
At some point you'll need to go into the details, but I don't think a comment is the right format. Maybe a blog post to show exactly what you mean.
At some point you'll need to go into the details, but I don't think a comment is the right format. Maybe a blog post to show exactly what you mean.
I specifically said the problem and the complexity inherent in solving it doesn't disappear with per-application databases.
But, the application (the 'A' part) is where the most context around the information is to be found. Tying multiple applications together at the Data-side (rather than the Application-side) means you don't lose that context... and eliminate your chances of clashing (and the ensuring integrity issues).