New idea: how about committing every packet into git and pushing it to a remote. You could even use webhooks to get notified of new packets!! This is all to, uh, take advantage of zero-rated traffic to github if that exists somewhere, I guess,
The satire in the title is reminiscent of how Firebase was born.
We were previously working on a chat system called Envolve (https://www.envolve.com), that was ‘Facebook Chat for any website’. A game that was using us for in-game chat created channels, used display: none on them, and passed game state through the chat.
We scratched our head, asked them why, and learned they wanted to focus on the frontend, not to deal with realtime message passing.
This led us to create a ‘headless version’ of our chat infra (re-written in Scala) that became the Firebase Realtime Database.
Really, if you are trying to avoid Managed NAT Gateway in production for egress-heavy workloads (such as webhooks that need to come from a common IP address), you should be using a Tailscale exit node with a public IPv4/IPv6 address attached to it.
How does this help you bypass the Managed NAT gateway? The only way I can imagine this working involves Tailscale eating the cloud egress costs for you which doesn’t seem like a sustainable idea.
Managed NAT gateway egress is $0.07/GB. Normal IP egress with a node that has a public IP is $0.01/GB. It’s like 7x more expensive to use Managed NAT gateway.
Wait. I read this whole thing thinking that any “savings” was because within AWS, bandwidth to S3 is free, intra-region, and relatively cheap otherwise. As you pointed out in the article, the API costs will get you. But, I guess I missed the tailscale connection.
Cursed. Incredibly cursed. This is bad and you should feel bad.
…well done.
Like Avian Carriers but in the cloud.
New idea: how about committing every packet into git and pushing it to a remote. You could even use webhooks to get notified of new packets!! This is all to, uh, take advantage of zero-rated traffic to github if that exists somewhere, I guess,
that is on the list for part 2: packetchain
With signed commit please.
Great work, and the cursedness reminds me of Tom7’s “harder drives”.
Tom7 has a new one out as of last month, GradIEEEnt half decent!
@cadey, I’d like you to know that I get the same rush of “yay!” from your work that I do from Tom7.
Oops, you just invented Firebase.
Funny you should mention that.
https://news.ycombinator.com/item?id=36187779
How does this help you bypass the Managed NAT gateway? The only way I can imagine this working involves Tailscale eating the cloud egress costs for you which doesn’t seem like a sustainable idea.
Managed NAT gateway egress is $0.07/GB. Normal IP egress with a node that has a public IP is $0.01/GB. It’s like 7x more expensive to use Managed NAT gateway.
Ah, I didn’t realize there was a price difference. I thought it was all just “egress”. Thanks for clarifying.
Wait. I read this whole thing thinking that any “savings” was because within AWS, bandwidth to S3 is free, intra-region, and relatively cheap otherwise. As you pointed out in the article, the API costs will get you. But, I guess I missed the tailscale connection.
Yes, but SIGBOVIK’s last conference was 2023… though, who knows if that’ll hold.
[Comment removed by author]