Show HN: I built a fuse box for microservices

Openfuse just dropped a “fuse box for microservices,” promising to stop failing services from melting down your app with one central brain and a neat dashboard. The pitch is simple: one line of code, synced circuit‑breakers across every server, free up to 10 “breakers,” and reliability for teams that live in the land of Stripe and other third‑party APIs.

But the crowd came in hot. whalesalad lands the mic‑drop: “what happens when your service goes down” — calling out the single‑point‑of‑failure elephant. dsl turns it into a meme with “a SaaS solution for making local outages global,” and suddenly “One breaker. Every server in sync.” is remixed as “One breaker. Everyone broke.” kkapelon worries about a herd effect: a tiny hiccup trips one instance, then everyone stops calling the service even if it’s already recovered. netik says the idea’s smart — but only on‑prem, citing round‑trip delays and asking what makes this better than a local cache that marks services down.

Meanwhile, cluckindan lights the DIY fire: why pay when a team can roll its own? Defenders argue centralized brains prevent split‑brain chaos and make tuning easy, but skeptics see vendor lock‑in and the possibility of flipping one switch that darkens the entire app. The comments are pure ops war stories and popcorn energy.