Read moreThank you for the additional information and clarity. We really do appreciate it.
However, not to be too critical, I have a question. The just of the issue seems to be that an update to the database of some sort caused performance issues, and since premier draft is (was) database heavy it suffered great degradation.
This is understandable as issues do slip through QA and mass load testing is never quite as accurate as the real deal. However why was the attempt to fix a P0 issue, in which the root cause analysis points to database performance, a complete rewrite of the drafting system, instead of a rollback of the database degradation update and an investigation into that? This article alone expressed the importance of taking time and doing QA on new features/updates, but yet it seems these changes were pretty major and rushed out in a panic as opposed to taking their proper time through the QA process. Was it not possible to revert the previous changes? And is there...
Rolling back the DB was an option that we investigated, but it ended up being much higher-risk than the changes to draft. This DB upgrade was also something that we had to take at some point (per the analogy with phone OS), so rolling back could only be a temporary solution