tl;dr

This week, the team will work on two fronts:

- Achieve the migration of 10% of the total repositories.

- Last week, we adapted our publication system to publish a document. This week, we want to support release publications.

- Start exploring the impact of the migration on the search and come back with the next steps.

Supporting the release of the media lib

Last week, we started the migration. No error patterns have been identified in the migrated repositories, indicating a smooth migration process up to this point.

An incident with the media library made us roll back the migration, but it won't have a significant impact on the overall progress.

We identified some ways to improve our rollback process. A comprehensive report will be created this week.

The focus for the upcoming week is to enhance efficiency by parallelizing the migration script. The objective is to migrate 10% of the total repositories by the end of this week.

We stay embedded in the Page Builder team, monitoring the migration.

Stripe Incident Update

The incident with the media library generated another incident with Stripe that flooded us with too many webhook calls to our writing room. We spent two days implementing a long-term solution to this issue. A report will be created this week.

PrismicDB Migration

In supporting the migration API to scale, we are still focusing on the PrismicDB migration. Last week, we reworked our publication system to support publication in the Core API. The goal for this week is to support the publication of a release.

We are launching a new spike to understand how to keep using Prismic DB to power the search and understand the impact on performance. We want to evaluate the necessity to start implementing the new search engine now or after the Prismic db migration.