Software engineering student focused on project management, with a strong dedication to continuous learning and development.
π Software Engineer by day, SRE magician by night! β¨ Tech enthusiast with an insatiable curiosity for data. π Harvard CS50 Undergrad igniting my passion for code. Currently delving into the MERN stack β because who doesn't love crafting seamless experiences from front to back? Join me on this exhilarating journey of embracing technology, penning insightful tech chronicles, and unraveling the mysteries of data! ππ§ Let's build, let's write, let's explore β all aboard the tech express! ππ #CodeAndCuriosity
Markdown supported Β· ββ΅ to post
Edge Ops
Circuit breakers and edge rate limits only help when open and closed states match real dependency health. Prefer a breaker that opens on a bounded error window against a named upstream, pair it with a coarser client rate limit so retries cannot reopen the circuit immediately, and degrade to a cached or static fallback rather than cascading failures into every caller. Keep the half-open probe budget tiny so a flapping dependency cannot thrash the pool.
Ops prove-out after enabling the breaker: dark the dependency and confirm callers trip open within the configured window, then restore it and watch half-open probes succeed before full traffic returns. Under a synthetic flood, confirm the rate limit sheds before the breaker storms the upstream. Compare p99 and origin error rate for one deploy β if both climb while the breaker still reports closed, thresholds are too loose or you are counting the wrong failure signal.