tl;dr

This week the team will have two major goals and a minor one:

- Completing last week's goal related to the database migration

- Upgrade users that are above their plan's limits to a plan that fits better their usage.

- Last week, we had a major incident on our Content API. We want to identify what to learn from it and better prepare to avoid similar incidents.

About last week's incident

We had a major incident last Thursday that had an impact on the content API for almost all our users for about five hours. We will take time this week to run a postmortem analysis, exploring what went wrong and what can be improved to prevent a similar incident. 

Upgrading users above their plan's limits

Two weeks ago, we started changing the plan's pricing but didn't change their plans. This time, we are planning to go a step further. We identified around a thousand user We will move them to a plan that fits with their current usage (i.e. the number of locales, the number of API calls, and the CDN consumption).

PrismicDB Migration

To ensure a seamless transition and consistent data across both databases, we plan to run the new and old databases concurrently in production for some time. This will allow us to compare and verify the integrity of identical data sets in both systems before definitely switching to the new system.

Key Milestone

We missed our goals last week, and are reporting them to this week. The goal remains to establish simultaneous communication with both databases. We aim to deploy this in production and conduct tests to confirm that selected repositories can effectively read and write data across both databases.