From Zero to Application Delivery with NixOS
summary
Company moves from Chef to Nix/NixOS on AWS to manage ~20–30 services (target 50), and uses Nixpkgs channels plus pinned versions to get repeatable dev environments and consistent CI dependencies. CI uses Jenkins builders that run Nix, repositories store both app and infra so a single git commit updates CI and deployment. NixOS modules generate VMs for testing, Nix can diff transitive paths for diffable dependency transparency, and node-level rollbacks become practical; Nixops AWS support and the learning curve remain the main drawbacks.
AI-written summary · about
chapters (36)
- 0:00Intro
- 0:19From Zero to Application Delivery
- 0:44% whoami
- 1:25Agenda
- 2:43Convergent Mayhem
- 5:49Why care about reliability now?
- 7:20More Services
- 8:01More Environments
- 8:56More Persistence
- 9:48Problem: Software Delivery
- 10:55Requirements: Optimize for .
- 11:21So what yields reliability?
- 11:33What allows you to reason about code?
- 12:06Functions have inputs (Scala)
- 12:25Functions have inputs (Nix)
- 12:57Packages have inputs (Nix)
- 14:50Functions return a result (Nix)
- 16:41Only depend on inputs (Nix)
- 18:35Return same result given same inputs
- 19:30The Big idea
- 20:50Mainstream Package Management
- 21:13Violates RT
- 22:40What Nix does ...
- 24:13Nix Ecosystem
- 27:05Repeatable Dev Envs
- 32:31Consistent CI Deps
- 35:58Diff Dependencies
- 36:28Predictable Deploys
- 39:00Test Machine Config (VM)
- 39:58Module Integration Testing
- 41:39Security Auditing
- 42:32Tradeoffs
- 44:33Benefits
- 45:05The Win!
- 45:21What Next?
- 46:18Where to Next?
related talks
34mNix for developers and ops
21m"I use NixOS btw..." Learnings from 2 years daily driving NixOS
01h 03mNixOS
06mNix: The declarative package manager
18mNix: FP for your packages and deployments
15mBuilding Developer-Friendly Spaces: Nix in a Nutshell
56mFunctional Infrastructure With Nix - Part 2 of 2
58mFunctional Infrastructure With Nix - Part 1 of 2