Beyond infrastructure as code DSLs
summary
Claims that Pulumi with TypeScript lets developers declare real infra instead of DSLs and shows it by building working systems on AWS: an S3 website plus a Lambda that converts uploaded Markdown to HTML, a shared VPC with an Aurora cluster and Fargate cluster, and Fargate-run migration tasks implemented as Pulumi dynamic resources that run, wait for exit codes and succeed. Covers stack references, component resources, outputs/Inputs, state backends (local S3 or Pulumi.com) and notes Pulumi.com adds locking, audit and policy enforcement for teams while S3 lacks locking.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 6:51What is Paluma
- 8:24Projects and Stacks
- 12:25State
- 15:31Plumie
- 17:39Static site generator
- 24:56Demo recap
- 26:46repo structure
- 27:46goals
- 31:59shared infrastructure
- 37:41Stack references
- 41:14Dynamic resources
- 42:14Fargate
- 43:14Polly Comm
- 44:39Demo
- 47:18Component resources
- 52:29Postman
- 54:57Recap
- 56:15Questions
related talks
44mInfrastructure as Software
49mInfrastructure as TypeScript
08mInfrastructure as code in any programming language
01h 01mCan TypeScript really make infrastructure management easy?
29mInfrastructure as Software
02h 31mPulumi, or How to Manage Your Infrastructure with Your Favorite Language
58mDeploying Cloud Infrastructure using Pulumi
53mInfrastructure as code - is it really?