2 ms·
Though it seems like a decent approach, I find it sad that this is necessary, since this slows down dev cycles. If AWS services were built on open standards, i
by jasonhansel 6y ago
Though it seems like a decent approach, I find it sad that this is necessary, since this slows down dev cycles. If AWS services were built on open standards, it would be easy to write local emulators and this whole problem would be fixed. Furthermore, if people avoided the nanoservice/serverless architecture the issue would be much less severe.
- nickthemagicman 6y agoThe idea sounds cool. No servers to manage. I don't know what to think though. A true language framework for backends is just so much better for me. There's Apache Openwhisk and OpenFass which are all open standards for serverless.
- jayair 6y agoI partly agree that it's weird that it takes something complicated to solve local development. That said, we've explored a wide range of options over the past few years and the local emulation route can be really hard to setup and ends up being pretty slow. I've personally gone back and forth on the idea of purely local vs cloud based development. And fwiw, SST strikes a very interesting balance between the two. You get the feel of a local environment, while still connecting to every cloud resource.
- benatkin 6y agoIt is only necessary if you choose "serverless" (somebody else's servers). Hey (the email service) has what should be an ideal use case for it but they're using Kubernetes instead.