We're definitely talking about different things. The open internet is hostile and you'll always need load shedding when the clients misbehave.
If you control all clients and servers and are on a closed network, you can do all sorts of fun things... though load shedding is helpful for when your good clients turn bad due to a code bug. A self DoS is the worst kind of outage.
IME sports doctors and physios have incentives aligned with returning to high functionality. I think this causes them to clinically converge on effective treatments. It’s also possible that they have clientele who are willing to put in the work to recover.
Regardless, if you’re optimizing for outcomes this is the way.
Having strong muscles around the joint won't fix a structural problem, but they definitely won't hurt.
When I tore my ACL doing bjj, I was surprised to see that some pro MMA fighters will continue to fight with a torn ACL. They double down on muscles to support the joint and postpone the loss of a year of competition to the reconstruction surgery.
Sounds half baked. What context does this function run in? Is it an interpreted language or an executable that you provide?
Inotify is the way to shovel these events out of the kernel, then userspace process rules apply. It's maybe not elegant from your pov, but it's simple.
No. You sit on the call and wait to restore your service to your users. There’s bullshit toil in disabling scale in as the outage gets longer.
Eventually, AWS has a VP of something dial in to your call to apologize. They’re unprepared and offer no new information. The get handed to a side call for executive bullshit.
AWS comes back. Your support rep only vaguely knows what’s going on. Your system serves some errors but digs out.
Google, Apple, and Meta (maybe others?) have the data to build a complete GeoIP dataset. None of them will share because there are only downsides to doing so.
When FB was rolling out ipv6 in 2012, well meaning engineers proposed releasing a v6 only GeoIP db (at the time, the public dbs were shit). Not surprisingly, it was shot down.
While I'm here: Google uses edns0 client subnet to geo target your client IP.
Try a dig -t txt o-o.myaddr.l.google.com @8.8.8.8 vs the others to see the src IP of the packet sent to Google's DNS server, and any edns0 info that came along with it.
How did they "win" when xds, envoy's config, is becoming the defacto interface to LBs? Sure, Gateway API is kinda xds by not, but it's envoy all the way down.
10 years ago at Facebook we had a systems design interview question called "botnet crawl" where the set up that I'd give would be:
I'm an entrepreneur who is going to get rich selling printed copies of Wikipedia. I'll pay you to fetch the content for me to print. You get 1000 compromised machines to use. Crawl Wikipedia and give me the data. Go.
Some candidates would (rightfully) point out that the entirety is available as an archive, so for "interviewing purposes" we'd have to ignore that fact.
If it went well, you would pivot back and forth: OK, you wrote a distributed crawler. Wikipedia hires you you to block it. What do you do? This cat and mouse game goes on indefinitely.
I worked on the laser printers in the early 2000s when they transitioned to Linux for the OS. They were hiring Linux nerds and I fit the bill. It was a fun place for a while, but the IBM legacy was an albatross. I left for Google and didn't look back.
Aktiia makes a continuous optical blood pressure monitor that is available in the EU. It's like wearing a fitbit, but for bp. You calibrate it with a pressure cuff once a month.
I'm pretty sure they're going through fda approval in the USA now.
If you control all clients and servers and are on a closed network, you can do all sorts of fun things... though load shedding is helpful for when your good clients turn bad due to a code bug. A self DoS is the worst kind of outage.