tl;dr

Our primary focus remains on scaling the document API by transitioning to a new database system.

We've refined our iteration process to prioritize thorough testing at each stage, rather than making last-minute adjustments.

Last Week's Goals:

Risk reduction for the migration:

Transitioning to a new database involves two pivotal tasks:

- Adapting the product to integrate with the new system.

- Migrating the existing data to the new database. Key business entities involved in this move include Documents, Document Versions, Locales, Releases, Custom Types, and Shared Slices.

We've chosen to prioritize the aspect of this project with the highest risk: data migration. Our approach involves adding business entities individually to the migration script, ensuring the script's reliability with each update. Each updated version undergoes a dry-run migration with all our active repositories. By running this nightly, we can identify and address any data inconsistencies well in advance of the actual migration. Importantly, these processes won't disrupt users' experiences in the writing room.

Last week, the team successfully merged everyone's contributions into a single piece of work. The migration script now supports Custom Types, Shared Slices, Documents, Releases, and Locales.

Goals for This Week:

We're back to operating at full team capacity this week.

Database migration:

- We aim to finalize the migration script by incorporating the final business entity: Document Versions.

- We're also set to start our dry-run migrations.

Once all entities have been migrated, our next steps will involve reestablishing the relationships between entities and rework how the product accesses data.