Please enable JavaScript.
Coggle requires JavaScript to display documents.
Jay Claringbold Team (reliability (Measures (Error Codes (HTTP Errors,…
Jay Claringbold Team
reliability
Measures
Latency
DataDog
System Metrics
Error Codes
HTTP Errors
Custom Codes
USer Sessions
Response Times
Security
Concerns
Monetary imapcts
FLAPI
Jobs
Talent Search
SLA's
Partners
Managing customer perception
Error Pages
Look terrible
Should never plan to create these
Seamless fallback on failures
Create some default messages
Customer experience should be a quality one no matter what the issue
Purpose
Seeks Customers shall not perceive
any downtime or degradation of our sites
services
Challenges
What if some downtime is acceptable
Do we knowingly want to provide customers with a poor experience?
Tradeoffs to this
People
Team structures
Tech Leads
Need to articulate well
Trade-offs
Costs of not doing
Edge cases
Importance
Effects
Help with Service requirements
Latency
Failures
Successes