Your team is transitioning from a monolithic architecture to microservices, and each service has its own database schema. How would you coordinate database migrations across multiple services to maintain data consistency and minimize downtime?

Assigning each microservice team the responsibility of managing its database migrations ensures that changes are aligned with the service's requirements and reduces coordination overhead. Implementing a centralized database migration service might introduce a single point of failure and increase complexity. Distributed transactions can lead to performance issues and tightly couple microservices. Adopting a shared-nothing architecture might provide isolation but doesn't inherently address coordination of schema changes and can increase operational complexity.