Intervista a Sarah Wells, Principal Engineer del Financial Times
summary
Microservices speed up releases to daily deployments with small, easily rolled-back changes, but they also multiply alert noise; the claim is that alerting must be only alert if you will act, otherwise teams drown. The practical prescription is threefold: design services for monitoring and support, make alerts actionable and high-signal, and treat monitoring as ongoing maintenance. Expect fewer false positives, faster incident resolution, and steady operational overhead if these rules are followed.
AI-written summary · about
related talks
01mWalking the tightrope: Balancing bias to action and planning
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
26mBeyond the Hype: Facing Micro Frontend Challenges in Large Scale
14mGrowing pains: Scaling and re-architecting systems under fire
23mA little less testing, a little more quality
13mOptimizing System Performance: O11y in Distributed Environments
35mCracking the WIP
51mIt's a Small World After All