Dashboard Platform Re-architecture

Three jobs were sharing one database and pulling against each other. The dashboards had to answer straight away for thousands of people checking them through the day. The reports had to grind through far more data than any dashboard touches. The overnight imports had to load large batches without either of the other two noticing. Something had to give, and it was always the dashboards — they are the ones with people sitting in front of them, waiting. So we split the data by how it gets read rather than by what it is. The dashboards now read from a second copy, kept in the shape they actually ask for, which turns a lookup into something closer to opening the right drawer than searching the whole building. The original records stay where they were and handle the reports and the everyday writing. Filtering was the other half of it: rather than write fresh code for every combination of filters someone might pick, one piece assembles the query from whatever they choose. From the outside nothing changed — the app asks for what it needs and never finds out there are now two places the answer can come from.