NixOS Architecture Note: Declarative System Design and Operational Boundaries
How to decide if NixOS fits your infrastructure, where trust boundaries sit, and how to check generations and garbage collection.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
How to decide if NixOS fits your infrastructure, where trust boundaries sit, and how to check generations and garbage collection.
NixOS makes system changes atomic by storing each activation as an immutable generation. Learn how to verify a rollback target and clean up safely.
Architecture note on how NixOS uses an immutable Nix store and generation pointers to provide atomic upgrades, rollback, and clear trust boundaries for declarative system configuration.
NixOS makes the running system a pure function of configuration.nix. nixos-rebuild switch builds an immutable generation and updates the bootloader atomically, giving instant rollback without manual restores.
NixOS makes a bad configuration change recoverable by keeping the previous system generation bootable. Here is how generations work, a worked SSH/user example, and the limits of rollback.