tl;dr

This Friday is Black Friday, and we have concerns with one client (Headout) this year.

We also want to achieve a first migration dry run to the new content database.

Goals for This Week:

Christmas Season preparation

Two weeks ago we had an incident with one of our clients (Bershka). Our API wasn't able to deliver their content for an extended time due to high traffic.

We conducted a root-cause analysis last week and want to implement some short-term solutions this week. One of them is a way to preload a ref in the API and we need to evaluate it first.

This process was challenging but helped us gain valuable knowledge on how e-commerce websites are launching their sales. For example, on sales day, Bershka is blocking its app until 7 pm and its website until 8 pm.

Keep progressing with the database migration

- Our new database (relational database) brings more rigour in the way we access and write data. It will prevent us from having the data inconsistencies that we can have with our current solution (non-relational database). We want to come up with a solution to fix all inconsistencies while migrating data.

- Migration data isn't enough if we can't access it. The team wants to validate all the work done to connect to the new database (data layer). It will be done through non-regression tests (unit test) and deployment in production (for 5 entities).