Getting Beyond FaaS: The PLONK Stack for Kubernetes Developers
summary
PLONK = Prometheus, Linkerd, OpenFaaS, NATS, Kubernetes maps concrete pieces to outcomes: PLONK = Prometheus, Linkerd, OpenFaaS, NATS, Kubernetes. A GitHub activity tracker using OpenFaaS, Postgres and NATS is built in a day and runs near-real-time; Prometheus drives autoscaling and alerts; Linkerd handles canary traffic and mTLS; NATS provides an async bus with callback URLs so long jobs (PDF generation) become background workers. Templates and a CLI shrink ~300 lines of YAML to a tiny CRD and get to production in minutes; OpenFaaS has ~250 contributors and 2,000 Slack users.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:14Monoliths (the good ole days)
- 2:03Cloud Native / Serverless Architecture
- 6:12What is the PLONK Stack?
- 23:01Case study - Ed Wilde @ Form3
- 28:28PLONK Stack users
- 33:02PLONK Layers
- 33:40Why PLONK is easier
- 34:38Connect & Learn
related talks
39mFaaS: A Contemporary, Comparative Study
37mServerless Functions for Beginners
23mOpenFaaS: Serverless platform with no strings attached?
39mBuilding Serverless Application Pipelines
31mBuilding a FaaS Platform Using CNCF OSS Projects (Knative, Crossplane, Tekton, ArgoCD)
28mBuilding a FaaS Platform Using CNCF OSS Projects
31mOpenFaaS Cloud + Linkerd: A Secure, Multi-Tenant Serverless Platform
37mAccelerating the Journey of an AI Algorithm to Production with OpenFaaS
