Shaping the Clouds - Introduction to TypeOps
summary
Yaga extracts TASTy metadata from compiled Scala jars, generates SDK glue and SBT packaging, and integrates with Pulumi so infrastructure definitions fail to compile if an application’s declared resources or schemas are missing. Current connector: AWS Lambdas with S3 thumbnail pipeline implemented end-to-end; codegen enforces compile-time verification of cross-service shapes and produced a compile error when a case class field changed. It shares data models via generated classes without classpath dependencies and reduces deployment boilerplate. Yaga aims to add OpenAPI, protobuf and Kubernetes connectors.
AI-written summary · about
chapters (9)
- 0:00Introduction to TypeOps
- 1:07Cloud systems challenges
- 4:20Infrastructure tools limits
- 6:27Types beyond applications
- 7:35Yaga core features
- 11:29Yaga internals and AWS Lambda
- 17:38Developer experience with Yaga
- 19:01Yaga and TypeOps future
- 22:12Competition and resources
related talks
01h 01mCan TypeScript really make infrastructure management easy?
39mFrom YAML to TypeScript - Developer’s View on Cloud Automation
42mIt (Only) Starts with Containers
51mScala At Netflix
38mScalaJS and Typescript: an unlikely romance
20mOne YAML To Rule Them All: Declarative Config
49mInfrastructure as TypeScript
06mKeynote: The Future of GitOps