I was talking about each silo of data; which is orthogonal to each monolith's code being refactorable. > If each business unit/domain has their own "monolith"

I was talking about each silo of data; which is orthogonal to each monolith's code being refactorable. > If each business unit/domain has their own "monolith" This furiously looks like accidental microserviced data; which is kind of ironic considering the original comment was about "Avoid microservices entirely". And yes, important business objects managed by different microservices are a PITA to merge; basically you're going to ask the users themselves to merge profiles, and they'll answer "we're divorced now" / "I like it better having multiple accounts, I get more promo codes" / "Why should I?" / "I don't care" / "Who are you?".