database-architect

To design a scalable database architecture, provide a high-level domain description and scale targets to receive a recommended data-layer design encompassing schema modeling, partitioning, replication, and governance strategies.

You need a zero-downtime database migration plan when re-architecting existing data stores or moving to a new database architecture, requiring versioned migrations and rollback plans to ensure continuous application availability.

Choosing between relational and NoSQL databases requires evaluating workload characteristics, operational complexity, and cost. Technology evaluation compares relational, NoSQL, and NewSQL options based on these specific project criteria.

Modeling database schemas for evolving data involves creating conceptual, logical, and physical models. It requires deciding between normalization and denormalization to plan effectively for future schema evolution and data growth.

Planning multi-tenancy and data governance involves designing partitioning, replication, and backup strategies. It ensures your scalable data layer meets compliance requirements while effectively isolating tenant data.

This database architecture approach works for both greenfield backend architecture projects and legacy migrations. It handles re-architecting existing data stores by evaluating operational complexity and providing structured migration planning.