tl;dr

This week, the team has 3 main goals:

- Release a new version of the bulk actions endpoints supporting the new database.

- Start adapting the legacy document editor to the new database.

- Start studying the integration of OpenSearch

- Fixing some billing bugs

Product adaptations

We are in the process of integrating a new database into the different systems of our product. The main idea is to make them able to communicate with the legacy and the new db simultaneously. We can monitor the new database behaviour using the legacy one as a source of truth. This is what we call the shadowing process. It will allow us to run the new system without taking the risk of a major incident involving data corruption in case of an issue.

Once done, we will switch to the new database.

We can't activate the shadowing process before having all sub-systems manage the new database. However, we can release progressively to ensure non-regression.

Last week, we released a new version of the custom type API and our Document API with the support of both databases.

This week, we are focusing on our next adaptations:

• the bulk actions sub-system
• and the legacy page builder

Integrating a new search

We defined a strategy to implement a new search engine a few weeks ago, going through intermediate steps.

We have decided to make a bet and work towards to the target search engine directly.

More to come soon.

Other topics

We will sync with the Page Builder team regarding integrating the bulk actions API in the core API to ensure we won't have a conflict in the future.