How Fly.io and Tailscale Saved Notado

Re:How Fly.io and Tailscale Saved Notado by dgentry on Monday October 17, 2022 @07:25PM (#33240899)

For me it was trying to build an AWS Lambda function where I'd deploy a new version and visit the URL, then wait for the CloudWatch logs. And wait. And wait. It might only be two minutes but that is long enough for me to want some tea, maybe look at some other issue filed that morning and see if I can make progress in diagnosing it, and WHOOPS I GOT DISTRACTED FOR HALF AN HOUR.

fly.io is instantaneous. I deploy, I see the result, I fix it, I deploy again and figure out the next problem. It is a pleasant environment to develop in.

[ Parent | on HN ]

Re:How Fly.io and Tailscale Saved Notado by akira2501 on Monday October 17, 2022 @10:27PM (#33242272)

I've noticed the time for new logs to appear is proportionally related to the number of log streams you have in that container already. If you eagerly spool your logs out of there and keep a short threshold for automatic deletion the request to log delay for a lambda serving something like API Gateway is, in my experience, only a few milliseconds.

[ Parent | on HN ]

Re:How Fly.io and Tailscale Saved Notado by ignoramous on Monday October 17, 2022 @10:47PM (#33242402)

> fly.io is instantaneous. I deploy, I see the result, I fix it, I deploy again and figure out the next problem.

Clearly, you haven't hit those spontaneous fly.io bugs, yet ;)

[ Parent | on HN ]