No, it absolutely does not. It might have in the past, when industry was booming in Germany and setup costs were huge and mistakes were very, very expensive.
However, they've pretty much lost the race when it comes to software and digitalization, where setup cost is pretty much non-existent, mistakes are inexpensive (fail early, fail fast), and ROI are generally multiples of 100%.
I'm always amazed at how people can make out anything without having the individual metal layers present as well to show vertical and horizontal connections in these die photographs.
It's not a proxy, but the 6to4 protocol that ISPs use to tunnel traffic. ISPs usually have IPv4s available, so they used it in the beginning of the IPv6 transition. However, there were quickly some problems discovered and the whole thing was deprecated after a few years.
> Rather than booking the replacement flight directly the author should have had easyjet rebook him.
Lol! I had experiences similar to OPs two or three times. Agents will actively refuse to rebook, if you can get a hold of them at all.
They will tell you all kinds of stories: "you booked through a third party, so your contract is with them and they need to rebook", or "I'm not allowed to rebook", or (another classic) "cannot be rebooked and you forfeit your compensation if you rebook yourself".
Honestly, at this point, I consider people suggesting rebooking through an agent as people who rarely or never fly and therefore are very naive about what actually happens in these types of situations.
That's a very nicely written and interesting article, bravo! Exactly why I come to Hacker News!
I always felt that Polish words were just too long because some many consonants are required to transport all the different sounds! I personally felt that Cyrillic would be a better fit, but obviously don't know the specifics having never learnt Polish (only a bit of Russian).
The choice of the old church symbols seems odd to me because they are so unwritable in handwriting and --- checking Wikipedia --- unsurprisingly evolved to look very different in cursive.
The point is that the image it draws contains the formula itself in readable text.
I agree that the presentation lacks a clear exposition of the author's goal --- at least for people unfamiliar with the rest of his blog, I presume.
I think it would be far more interesting how to actually construct this formula than just presenting the formula itself, though...
"The world needs more {model-based,model-driven,low-code} software engineering", cried the dumbass sitting in front of Matlab screwing up a signed comparison. sigh
There was a reason it was the dining room. The guy wanted to make you feel comfortable, forget all about the deposition and just have a chat... so he can nail you to the cross with your own words.
The author seems to think completely in terms of "wasted utilization" when it comes to timeouts. I think they are missing the point of the timeouts and the retry logic to begin with. The effort by the circuit breaker isn't wasted, because it is exactly trying to establish whether a resource is responding or not taking into account occasional network hiccups.
If every effort past the initial timeouts was wasted, then why implement this logic to begin with?
I agree with derefr (https://news.ycombinator.com/item?id=22546241) in the sense that it seems illogical to increase latency for users simply to check for availability of a timed-out resource.
IMHO the worst-case assumption of all service instances failing simultaneously leads the author astray in their quest to reduce "wasted utilization".
Pretend the network switch rebooted and all services were unavailable for a short period of time, but your website is in high demand, so the error threshold of three errors per resource was quickly reached.
Let's pretend the network switch needed 5 seconds to reboot, so 42 resources each failing 3 times in that time equals 126 requests/5 seconds, 25.2 requests/second. Now, instead of quickly recovering from that state after two seconds, the author advises to instead wait 30 seconds, so that's 756 requests---because your site is so popular---before the first service is retried. Then an additional 41 requests (~1.67 seconds) until all resources are marked available again. So now you made about one thousand people unhappy in case it's their browsing session that's constantly lost.
Unless of course your were too optimistic when setting the half_open_resource_timeout, because then your services might be blocked for multiples of error_timeouts, e.g. minutes with a high error_timeout value of 30 seconds. That's a lot more than a thousand people unable to log in.
IMHO setting the half_open_resource_timeout way lower than the regular service_timeout value will just risk the services _never_ becoming available again after an internal network outage in your data center. That seems like a recipe for disaster.
> Wait, actually this whole sentence is just entirely an insult. You've completely dismissed any opposition as 'insane' or 'abnormal' or 'not well adjusted'.