How Do Tech Teams Diagnose Architecture Problems?

Key Takeaways

The first thing I look at is mapping the data layer, schema, how data flows, what's denormalized, where the real bottlenecks >> [music] >> are. Data is sticky. Code you can rewrite, but data structures define what's possible and not possible. Then we [music] trace the dependency graph, what's tightly coupled, where there integration points. [music] Then we run load tests under realistic traffic to find where the actual pain points [music] are versus just the theoretical ones. Then we talk to the people who've maintained this thing. They're going to know where where all the monsters and dragons are.