3 ms·

i found a lot difficult, like: - how to structure my code, esp wrt callbacks/ step functions - are there any conventions? like, what should my handler be c

i found a lot difficult, like: - how to structure my code, esp wrt callbacks/ step functions - are there any conventions? like, what should my handler be called? - uploading libraries (into/via layers) was stupid - no ability to decomission lambdas -- you just gotta delete 'em - finding lambdas was painful; the console was slow - linking them to api gateways and configuring was painful i'm still a fan of the general concept, but once i got past 'hello, world', the dev cycle slowed down tremendously.

hzlatar 5y ago
Thanks. That's exactly the kind of answer I'd hope I would get. Precise and actionable. Admittedly, I'm a fan of serverless. I believe serverless will soon become a dominant form of cloud computing. I think it is just a matter of immaturity of the platforms and lack of tools. While I can't do much about the platforms, I can try to build better tools. That's what my team and I are doing with Mantil https://github.com/mantil-io/mantil https://github.com/mantil-io/mantil
garethmcc 5y ago
This is where using a tool like the Serverless Framework helps solve a lot of these problems: - Use async/await promises instead and the specific plugin for the Serverless Framework for configuring your Step Functions makes it easy! - Nothing specific here but just call it hat makes sense. - Use your runtimes dependancy management tool. NPM for Node for example - Just us "serverless remove" (you used "serverless deploy" to set them up) - No need for the console with the Serverless Framework - Use Serverless Framework. Literally 3 lines of yml configuration and you are done. https://www.serverless.com/framework/docs/providers/aws/events/http-api https://www.serverless.com/framework/docs/providers/aws/even... The dev cycle can be super fast. I have never before built stuff so quickly. Using "serverless deploy function -f functionName" means I can push my code changes into the cloud in 3 seconds for testing purposes so need to even setup local testing environments which can get very complex and be totally inaccurate compared to the environment that exists in AWS

hzlatar 5y ago

Thanks. That's exactly the kind of answer I'd hope I would get. Precise and actionable. Admittedly, I'm a fan of serverless. I believe serverless will soon become a dominant form of cloud computing. I think it is just a matter of immaturity of the platforms and lack of tools. While I can't do much about the platforms, I can try to build better tools. That's what my team and I are doing with Mantil https://github.com/mantil-io/mantil https://github.com/mantil-io/mantil

garethmcc 5y ago

This is where using a tool like the Serverless Framework helps solve a lot of these problems: - Use async/await promises instead and the specific plugin for the Serverless Framework for configuring your Step Functions makes it easy! - Nothing specific here but just call it hat makes sense. - Use your runtimes dependancy management tool. NPM for Node for example - Just us "serverless remove" (you used "serverless deploy" to set them up) - No need for the console with the Serverless Framework - Use Serverless Framework. Literally 3 lines of yml configuration and you are done. https://www.serverless.com/framework/docs/providers/aws/events/http-api https://www.serverless.com/framework/docs/providers/aws/even... The dev cycle can be super fast. I have never before built stuff so quickly. Using "serverless deploy function -f functionName" means I can push my code changes into the cloud in 3 seconds for testing purposes so need to even setup local testing environments which can get very complex and be totally inaccurate compared to the environment that exists in AWS