3 ms·
Readers who are unfamiliar with SST would do well to read a bit about the project, the backing company, and the work they've been doing. Things have come around
by solatic 2y ago
Readers who are unfamiliar with SST would do well to read a bit about the project, the backing company, and the work they've been doing. Things have come around full-bore from serverless-only on AWS via CDK, putting huge effort into trying to make CDK fast and seamless, realizing they needed to support more than AWS and that CDK/CF are just too slow, transitioning into a Pulumi backend, supporting other clouds, and now, containers.
SST is great because they built a model for infra-as-code that gives sensible defaults out-of-the-box while preserving enormous flexibility as the architecture grows, plus great conventions around giving code access to the environment details via bindings.
Super excited to play with this.
- swyx 2y agodoes SST compile to CF? for serverless stuff (and now the limited container stuff) what are the tradeoffs SST has vs CDK?
- jackbravo 2y agoIt's built on top of pulumi, and their docs have some comparison against both CDK and pulumi in their FAQ section: https://sst.dev/docs/#faq https://sst.dev/docs/#faq
- wrs 2y agoIt used to use CDK/CF. There’s a long blog post about them deciding CF is unusably bad and moving to Pulumi this year. https://sst.dev/blog/sst-v3/ https://sst.dev/blog/sst-v3/