Tailscale and scale
2024-07-27 16:16:14.643431+02 by Dan Lyke 3 comments
I read a post recently where someone bragged about using kubernetes to scale all the way up to 500,000 page views per month. But that’s 0.2 requests per second. I could serve that from my phone, on battery power, and it would spend most of its time asleep.
In modern computing, we tolerate long builds, and then docker builds, and uploading to container stores, and multi-minute deploy times before the program runs, and even longer times before the log output gets uploaded to somewhere you can see it, all because we’ve been tricked into this idea that everything has to scale. People get excited about deploying to the latest upstart container hosting service because it only takes tens of seconds to roll out, instead of minutes. But on my slow computer in the 1990s, I could run a perl or python program that started in milliseconds and served way more than 0.2 requests per second, and printed logs to stderr right away so I could edit-run-debug over and over again, multiple times per minute.
Holy crap, yes, that's the right attitude. I just checked, this < $10/month Hetzner instance is serving on the order of 600k requests/month. But it also makes me super interested in Tailscale, which seems to be a framework for actual peer to peer Internet communication the way we used to envision it back in the days of protocols like finger, albeit with some authentication layers over it.
I'm intrigued.
Via.