Avoid Artificial Stupidity
This seems like a common side-effect of an overly segmented microservice architecture.<p>I’ve noticed this pattern numerous times, my guess is service/feature teams want to avoid at all costs taking another service dependency (and all the testing and coordination that entails) so they just punt.<p>Sometimes a big old RDBMS housing all of your data <i>which is actually already related in reality</i> makes the most sense.