Nelson - Functional programming in system design
summary
Nelson is a deployment orchestration system that enforces immutable deployments by tracking explicit service name+version dependencies and publishing that graph to service discovery. Repos supply a Nelson manifest plus a per-release deployable; GitHub deployments or the CLI slipway trigger webhooks that cause Nelson to provision Vault credentials, write discovery entries (Consul or Kubernetes), and submit templated scheduler specs called blueprints. It supports Kubernetes backends, automatic traffic shifting, lifecycle cleanup, and multi‑datacenter schedulers.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 15:09Conceptual basis of Nelson
- 21:53User perspective and workflow
- 29:11Operator perspective and blueprints
- 33:24Roadmap and future plans
- 34:29Q&A on dependencies and workflows
related talks
43mNelson: Rigorous Deployment for a Functional World
41m"Architecting systems through Engineering Principles"
36mYou Might Just be a Functional Programmer Now
06mRyan Delucchi Interview
27mThrough the Looking Glass: Leveraging Overton Window Concepts To Redefin...
32mFunctional Programming for (Dev)Operations and Infrastructure
35mInto the Shopfloor: Moving Manufacturing Execution Systems To Kubernetes
53mChange your tools, change your outcome