Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
h2odragon
on April 8, 2021
|
parent
|
context
|
favorite
| on:
Surprisingly Slow
I'll throw in "hidden network dependencies / name resolution"; it's amazing how things break nowadays when there's no net.
iudqnolq
on April 8, 2021
|
next
[–]
For years I thought sudo just had to take seconds to startup. Then one day I stumbled across the fact that this is caused by a missing entry in /etc/hosts. I still don't understand why this is necessary.
https://serverfault.com/a/41820
segmondy
on April 8, 2021
|
prev
|
next
[–]
Number one rule of distributed systems, "the network is not reliable"
donw
on April 8, 2021
|
parent
|
next
[–]
Also the number one rule of Comcast.
verdverm
on April 8, 2021
|
root
|
parent
|
next
[–]
https://github.com/tylertreat/comcast
donw
on April 8, 2021
|
root
|
parent
|
next
[–]
I have actually used this to test remote pair-programming tools, as remote pairing really hinges on latency.
aitchnyu
on April 8, 2021
|
root
|
parent
|
prev
|
next
[–]
If we have a pesky test suite with failing latency tests
https://github.com/auchenberg/volkswagen
pjmlp
on April 8, 2021
|
parent
|
prev
|
next
[–]
Second rule, trust no one.
verdverm
on April 8, 2021
|
prev
[–]
I'd add SaaS dependencies as well, whether it be slowness or downtime
segmondy
on April 8, 2021
|
parent
[–]
This is a solved problem tho, timeout / retry / circuit breakers / fallback etc.
See -
https://github.com/resilience4j/resilience4j
verdverm
on April 8, 2021
|
root
|
parent
[–]
I wouldn't call it solved if a downstream SaaS is down and my build still times out despite the aforementioned resiliency.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: