In SWATCH-3679, we documented what the successful pattern we used was. When we established that pattern, we had a monolith application/database. Now that we're more aligned with a typical Service Oriented Architecture, we should investigate best practices for large database changes that reduce risk and ideally avoid taking an outage to complete.

Acceptance Criteria:

• Documentation of the current pattern, alternatives explored, and proposal of what our pattern should be going forward
• Meeting with the team to align on pattern going forward
• InScope document from SWATCH-3679 updated accordingly