Infrastructure-as-code is a misnomer - more like infrastructure-as-text. It lacks many of the affordances that we expect when developing applications.
Attended a great #QConSF talk by @lukehoban where he demonstrated infrastructure and code, both as TypeScript, living as one!
-
-
agreed - I favour serverless and their use of YAML, but only because it is more terse, not because it is a fundamentally better option. However, what really stood out in this talk was infrastructure code and application code living right next to each other in the same place.
-
The jury is still out there on whether this is a clean scalable thing.. but I like Pulumis approach for infra in Typescript/C#/go whatever
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.