@moretea_nl

@moretea

research engineer

@

our clients

goal for user clients

• improve time to market
• enable experimentation

means

• CI/CD
• cloud native architecture

Tech at our user clients

• Docker
• Micro services
• Orchestrator
  • Kubernetes
  • Mesos

Nix

Socks shop

• Covered
  • Build
  • Deploy
• Not covered
  • CI server Hydra
  • Binary Caches

Microservice reference app

• Different languages
• Several deployment targets
  • Kubernetes
  • Swarm
  • Mesos
  • AWS ECS
  • ...
• Packaged as Docker containers

scope

• Build
  • Create packages
  • Manage all dependencies
• Deployment
  • Configuration management system
  • Cloud resource provisioning

Tools

• nixlang
• nixpkgs
• NixOS
• NixOps

Why bother?

we already have

• • Terraform
  • CloudFormation
• • Ansible
  • Chef
  • Puppet
• • Docker
  • Rkt

One language to rule them all!

• Simple
• FP
• Pure

therefore composable

• Layers do not compose well
• Graphs do

Building

• Ruby application (dev-env demo). Nokogiri
• Go application
  • (and how to write two support two different vendor managers)
• Node application

Deploying

• Docker / AC images
• Nix containers
• NixOps

NixOps

• Local
• GCE

• Covered
  • Build
  • Deploy
• Not covered
  • CI server Hydra
  • Binary Caches

Advantages

• One language to rule them all
• Predictable
• 100% identical development environments

Disadvantages

• Either something works immediately, or it takes quite some time
• Smaller eco-system
• Only reference manual, no 'guides'

• #nixos on FreeNode
• Email list
• https://www.meetup.com/Amsterdam-Nix-Meetup/