Hypergrowth can be natural. Random example but what if you designed a microblogging service and all of the sudden the biggest platform gets bought by a facist and users come flocking? You could start turning users away or you could work as fast as you can to accommodate them and make small mistakes along the way. Both of these are reasonable decisions and neither one is really wrong.
> Hypergrowth is a synonym for unsustainable growth. The headline here is business breaks tech, again.
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.
I use the built in derp server. I have run a standalone derp server hackily deployed for a month, it worked fine but didn't provide much benefit over the built in one. It was basically just a go package. If you're familiar with running Go code, it's straight forward to run, it's very, very light/unproductionised.
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.
TailScale is a VPN, and the article highlights a recent increase in user base. This is likely due to VPNs being required to access pornographic materials for residents of many US states.
It could also be that Tailscale users have many kids, who then also use Tailscale. Although if the header is meant to represent that, it's showing the wrong position.
Notably, it's a VPN for connecting your own devices together, so unless you're deploying a server elsewhere for access to porn it's probably not for that.
Would you mind explaining this comment? (I worked on deviantart for many years when it started so I'm curious, tho the servers did literally melt at one point)
pack considerably more spinning disks bought off the shelf at radioshack than you ever reasonably should in a box in a colo, turns out they generate a lot of heat, I don't recall the year I'd guess around 2004/5-ish - was a big problem, site was down for quite some time. Same year someone found out who one of our mods was and showed up to their house with a gun. Ask me about hypergrowth, I'm not sure if the DeviantART stories or the DigitalOcean stories are more wild. heh. :)
Kind of annoying to read. No, the P in CAP theorem isn’t when the client can’t connect to your unavailable service. That would be the A. Maybe it was down because of a P on your side, but don’t start blaming your downtime on network partitions between the client and your service.
Edit: your service going down and not being able to take requests from clients does not a network partition make
This is a common misunderstanding about the poorly named ‘Availability’ in CAP. Availability under CAP means that if your request reaches a non-failing node, that node still responds despite being unable to communicate with other nodes. This is distinct from SLA-style availability, which describes the uptime of the overall system.
I’m pretty sure the partition tolerance they’re referring to is the fact that the tailnet remains intact and continues to operate even when nodes can’t reach the coordination service.
Not if most of your company was built on investor money.
They want their pay day!
Tailscale is great technology and protocol and facilitates decentralisation.
Hypergrowth is a synonym for unsustainable growth. The headline here is business breaks tech, again.
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.
[0]: https://headscale.net/stable/setup/requirements/#ports-in-us...
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
Same in the UK, recently.
https://www.bbc.com/news/articles/cvg5er4ewg6o
a specific type of porn
Edit: your service going down and not being able to take requests from clients does not a network partition make