Functional programming and Nix for reproducible, immutable infrastructure
summary
Atlassian Marketplace uses Nix end-to-end: Nix expressions compile to content‑addressed .drv files, builds are bit-for-bit reproducible and cached, and Docker images are produced without a daemon or Dockerfiles. The team runs the same Nix definitions for CI, local dev shells, and production images on the internal PaaS, with every dependency hash‑pinned so the exact libc, language runtimes and package versions are known and repeatable.
AI-written summary · about
chapters (14)
- 0:00Introduction to Nix
- 1:54The philosophy of functional configuration
- 6:33Comparing configuration models
- 9:10Practical applications of Nix
- 10:28Functional package management
- 14:07Derivations and build definitions
- 17:28Realization and reproducibility
- 20:44NixOS and operating systems
- 22:23System management and generations
- 23:58Development shells
- 26:01Building Docker images
- 28:09Declarative image generation
- 30:12Key benefits and summary
- 31:33Q&A session
related talks
58mFunctional Infrastructure With Nix - Part 1 of 2
34mNix for developers and ops
40mBut It Builds on My Machine!: Building Deterministic OCI Images With Nix
06mNix: The declarative package manager
01h 03mNixOS
31mNix: Need an Ultra-Robust Dev Environment? Create an Immutable, Reproducible Env
15mBuilding Developer-Friendly Spaces: Nix in a Nutshell
59mReproducable environments using nix