How would you handle a practical scenario involving Database per Service in Microservices Architecture?

For a practical scenario involving Database per Service, I would first clarify the business goal, scale, constraints, and the failure or quality attribute being tested. Database per service means each microservice owns its persistence and other services access that data only through defined contracts. The scenario centers on a reporting feature needs data from orders and payments; explain alternatives to direct cross-database joins. For production, keep data ownership explicit, expose APIs or events for sharing data, use read models when needed, and avoid distributed joins across service databases. I would then compare the main alternatives and tradeoffs, identify likely failure modes, and explain how I would validate the solution through testing, observability, security controls, and recovery or rollback planning.