Viewing profile — dyanacek
dyanacek
HN member- Joined
- Thu, Dec 05, 2019, 5:48 PM UTC
- HN karma
- 31
- Public activity
- 8 items
- HN profile
- View on Hacker News ↗
About dyanacek
No profile information was provided.
Recent public activity
-
comment
Comment #28819978
Yes! LIFO is a fantastic improvement. This suggestion is buried in the article a bit. Maybe I should have elevated it, or maybe broken it into more pieces. There’s so much to talk …
-
comment
Comment #28819942
Good point around avoiding the call in the first place. This is a very tricky topic, I’ve found. Things that try to guess the nuanced health of a dependency can lead to outages whe…
-
comment
Comment #28819686
These remain as great techniques! Even iptables like you mention - it’s extremely good at cheaply shedding new handshakes, vs later on in processing the request. You lose a little …
-
comment
Comment #28819627
Agreed - utilization is an important consideration here. The capacity red line will still be there, but when load shedding is effective, the impact of crossing that red line is les…
-
comment
Comment #28819494
It’s a tricky topic because load shedding is a last resort that kicks in when there’s already a problem. So until auto scaling catches up or the issue is mitigated some other way, …
-
comment
Comment #28819455
This is a great way to describe it! I gave a similar example of pagination and how the later pages might be better to prioritize over initial pagination requests, but your example …
-
comment
Comment #21727494
Good point. We should use more images. I’ll think about where we can add some for clarity! Now that we’ve done a bunch of talks at reinvent in these topics, we should have some tha…
-
comment
Comment #21719035
One of the authors here. I agree with all the folks’ suggestions here! When I was in college, I took extra writing courses beyond what was required for an engineering degree (they …