Working with Third Parties Shouldn't Suck
summary
Argues third parties must be treated as part of the stack, not optional extras, and gives concrete practices: run RFI/RFPs, demand timely, direct answers, require SLA credits and detailed RCAs, and keep scorecards. Recounts a major DNS outage that cascades and “took down about half the Internet,” notes 89% and 92% of companies expect third-party impact, and describes building automation at LinkedIn to run six CDNs with a service-integration manager, using synthetic + real-user monitoring, logging, and a quarter-long procurement cadence.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:34Setting the Stage
- 3:13What's a Third-Party?
- 5:16What's my deal?
- 6:34Build vs. Buy vs. Adopt
- 8:05Questions to ask yourself..
- 9:24Weighing Risks and Benefits
- 10:30Request for Information / Proposal
- 12:16Trial Time
- 14:26Keeping Score
- 16:34Neverending Story of Third-Party Integrations
- 21:07Logging / Auditing
- 22:48Tooling / Automation
- 24:20Plan for Failure
- 27:48Take Aways
related talks
35mEffective Handling of Third-Party Supplier Incidents
31mRadical Ideas Enterprises Can Learn From The Cloud
28mReliability Lessons from Running High Traffic Services for More Than 10 Years
22mDon’t wait for an outage to improve your reliability
22mWhy is it always DNS, TLS, and bad configs?
27mTrusting Mission Critical Infrastructure: Building Reliable CD P...
37mEmbracing the Multi-Party Dilemma: Incident Response Across...
15mMaintaining reliable systems