Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Astra for Law(openai.com ↗)
    206comments
  2. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    100comments
  3. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    25comments
  4. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    120comments
  5. Wax motor(wikipedia.org ↗)
    37comments
  6. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    174comments
  7. Sex, AI, and the Apocalypse(iankduncan.com ↗)
    22comments
  8. Flet 1.0 – Build cross-platform apps in Python(flet.dev ↗)
    3comments
  9. CrowdSec Source Code Leak(crowdsec.net ↗)
    34comments
  10. How to Write with an LLM(sockpuppet.org ↗)
    4comments
  11. Rate limits on GitLab.com are changing(about.gitlab.com ↗)
    103comments
  12. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data(arxiv.org ↗)
    26comments
  13. Everybody's Lost Their Minds(netmeister.org ↗)
    169comments
  14. Diplodocus, Long Thought Exclusively American, Turns Up in Spain(sci.news ↗)
    3comments
  15. The American Religion of Self-Storage Facilities(newyorker.com ↗)
    292comments
  16. How Uber Protects Against Retry Storms(uber.com ↗)
    6comments
  17. How GLM built its own inference infrastructure(z.ai ↗)
    254comments
  18. Zettascale (YC S24) Is Hiring ASIC/FPGA Engineers to Build Chips for ASI(zscc.ai ↗)
    discuss
  19. TSMC revealing details about next gen A14 node(mapyourshow.com ↗)
    27comments
  20. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    240comments
  21. Show HN: Snapdrop: Instantly share files between devices. No setup, no signup(snapdrop.me ↗)
    6comments
  22. How do we prevent mathemathics from devolving into the Medieval Era of secrecy?(mathoverflow.net ↗)
    29comments
  23. Running Ubuntu on the Lenovo IdeaPad Duet(vhaudiquet.fr ↗)
    18comments
  24. One year of sponsored Servo development(servo.org ↗)
    136comments
  25. Canto: A speech model built for the real world(wisprflow.ai ↗)
    11comments
  26. André Weil and the Hodge Conjecture(jiahao116.github.io ↗)
    8comments
  27. CCC invites all model citizens to 40C3(ccc.de ↗)
    175comments
  28. Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents
    43comments
  29. Towards Self-Driving Codebases(detail.dev ↗)
    74comments
  30. Show HN: Share your AI Setup, Learn from others(mysetup.ai ↗)
    82comments

How Uber Protects Against Retry Storms

9 pointsby 1h agouber.com
1 comments
20m agoHN ↗

I'd be interested to hear other strategies in this space. I've done the naive thing of allowing retries everywhere, and gotten into retry storms. When I was next presented with the problem, I tried the other naive thing of only allowing retries from the very top level service, which led me to redoing absolutely tons of work for each failure. What's a nice middle path that doesn't add too much complexity?