I cannot possibly understand why you would do that.
You're dropping the ability to do trivial joins, trivial reporting, trivial SQL aggregates, over... what, exactly?
You're dropping the ability to do trivial joins, trivial reporting, trivial SQL aggregates, over... what, exactly?
If you can perform a join to get the data yourself, nothing is stopping anyone from circumventing your API that is intended for fetching the data or by making breaking changes to the single database that your code relies on.
But yes, trivial joins is effectively the trade off for this encapsulation and can mean other services have to collect their own versions of data from services which means you now have eventual consistency.