Work

A few learnings from launch morning:

At our highest traffic points, Web server and DB server performance were never even close to hitting any limits whether CPU, memory, disk space, etc
Caching was a big win, at least in the short term
Our code felt sloppily crafted. What I mean is:
1. Routes like the Orders API bulk preview route were grossly inefficient. While it was (apparently) created to allow doing multiple previews at once, it appear that zero thought was put into actually taking advantage of doing this in bulk and/or parallel
2. Caching was not carefully implement (ie, not implement at all in obvious places)
3. We have a ridiculous web of interconnected microservices. Discounts, orders, products, subscriptions--none of them are stand-alone services. They all depend on each others, it seems. I believe there has not be careful planning around the boundaries of these APIs and, unless replatforming supplants them completely, we need some major overhaul or at least strongly-worded guided on incremental improvements as we maintain these services
I see a couple of potential causes for this "carelessness":
1. Our most experienced senior engineer (who also had the most senior insight into what Commerce was doing) leaving two months before launch (Nate Merritt)

Meetings