Same in the UK, recently.
Tailscale is great technology and protocol and facilitates decentralisation.
Hypergrowth is a synonym for unsustainable growth. The headline here is business breaks tech, again.
No it's not. It's often a recognition that just one or two, maybe three companies will end up dominating a particular market simply due to economies of scale and network effects... and so the choice is between hypergrowth to try to attain/keep the #1 or #2 position, or else go out of business and lose all the time, money, and effort you already put into it.
Nothing whatsoever makes it unsustainable. You might be offering cheaper prices during hypergrowth -- those are unsustainable -- but then you raise prices back to sustainable levels afterwards. And consumers got to benefit from the subsidized prices, yay! The business is entirely sustainable, however.
Uber is the poster child of hypergrowth. They became profitable in 2023. And their stock price has ~doubled since. Totally sustainable.
That just isn't true. Plenty of services do just fine after experiencing hypergrowth, and a few outages are not an example of tech breaking. That's a fairly common occurrence.
And I disagree: outages are a fairly literal example of tech breaking. A few outages aren't catastrophic though, and I agree are fairly common. I know it's cliche, but "move fast and break things" might get growth, but it also gets broken things along the way.
Hypergrowth is growth and churn at the expense of sustainability and stability. It can definitely be fun though!
[0]: https://headscale.net/stable/setup/requirements/#ports-in-us...
https://tailscale.com/kb/1118/custom-derp-servers
My last company ran our own DERP servers to have more consistent endpoints we controlled
I have a todo task to integrate derp into my headscale deployment properly ("finish ansible role"), but when I picked it up last month, I noticed tailscale had release relay nodes, and they seem like they'd be better suited than dedicated derp nodes, but headscale hasn't implemented support for them yet.
tldr: not to hard to host DERP, just needs publicly facing endpoint (incl. letsencrypt) but the built in one is fine. But relay nodes look like they'll be a better option for most and I'd guess will be implemented in headscale sometime this year.
So, things are working as designed for the few people that benefit
Caveat: I have a very small tailnet (<100 nodes). Anyone running with thousands of nodes may have a very different experience where inconvenience might be existential.
(There is Headscale though)
Instead, I think of hypergrowth as a supply-side attempt to capture a larger market in a highly inorganic way and to also capture the absurdly high valuation that comes with it. Usually through VC.
Not if most of your company was built on investor money.
They want their pay day!
Edit: your service going down and not being able to take requests from clients does not a network partition make
When I reconnect, my dating profile is missing all the pictures I uploaded of me in my new convertible with me lowering my sunglasses and winking at the camera.
The LovinHuggin.com server architecture is Available, but not Partition Tolerant. And after I upload different pictures of me in tuxedos and talking like a boss on the cellphone to region B, I've potentially created a weird "split brain" situation. Region A and region B servers have different views of me. Both views are super hot, but the client might get confused if my session returns to region A when their network heals, and the nightly region replication might be messy with reconciling the split brain. Eventual consistency is a helpful (or fraught) feature to have in the database when things like split brain happen.
