When Compliance Becomes Architecture
NIS2 and DORA usually get discussed as paperwork and lawyer territory. But if you actually read them, these obligations translate directly into architecture constraints. The mandate for an "exit strategy" actually means your infrastructure must be portable. The strict 24-to-72 hour incident reporting windows (NIS2) mean you can't waste days mapping the blast radius; your system inventory needs to be instantly queryable. And the requirement for "operational resilience" means a single component failure must be contained before it cascades into a disaster.In this session we set the compliance side aside and look at the engineering problems these rules actually create. For each one we see where the constraint bites, why it is hard to solve, and how you solve it in practice using Fractal Cloud as a concrete example.