The document discusses strategies for ensuring availability in cloud operations, emphasizing the importance of design for failure and proactive monitoring, especially during peak times like Cyber Monday and Black Friday. It mentions various technical aspects such as continuous integration, session replication, and the importance of avoiding OS lock-in. Additionally, it includes disclaimers regarding IBM's product information and performance projections, highlighting that actual results may vary for users.

1. Brian O’Connell
@boc_tothefuture
linkedin.com/in/broconne
Avoid the Fail Whale
Design for Availability

2. 2x
Cyber Monday
+
Black Friday

3. $17.8B / day
2x
Cyber Monday
+
Black Friday

4. $972k / sec
2x
Cyber Monday
+
Black Friday
$17.8B / day

5. Domain Cloud Operations Application
Sports

6. Enterprise
Domain Cloud Operations Application

7. Hybrid
Cloud
Domain Cloud Operations Application

8. Cloud
+
Ops
+
Dev
Domain Cloud Operations Application

9. 3 or 4 Locations
Domain Cloud Operations Application

10. $$$
2 > 3
Domain Cloud Operations Application

11. Identical
Domain Cloud Operations Application

12. Automate
Domain Cloud Operations Application

13. No HA Takeover
Domain Cloud Operations Application

14. Global Traffic
Management
Domain Cloud Operations Application

15. Stand Ups
Domain Cloud Operations Application

16. Global
Staff
Domain Cloud Operations Application

17. Technical
Leader
Domain Cloud Operations Application

18. Squads
Domain Cloud Operations Application

19. Proactive
Monitoring
Domain Cloud Operations Application

20. Change
Orchestration
Domain Cloud Operations Application

21. Business Hours
Changes
Domain Cloud Operations Application

22. Slack
IRC
Domain Cloud Operations Application

23. Single Pane
of Glass
Domain Cloud Operations Application

24. De-Advertise
Domain Cloud Operations Application

25. Maintenance
Domain Cloud Operations Application

26. CAP Theorem
Domain Cloud Operations Application

27. Consistency
Domain Cloud Operations Application

28. Availability
Domain Cloud Operations Application

29. Partition
Tolerance
Domain Cloud Operations Application

30. Systems of
Engagement
Domain Cloud Operations Application

31. Financial Data
Domain Cloud Operations Application

32. Session
Replication
Domain Cloud Operations Application

33. Bi – Directional
P2P Replication
Domain Cloud Operations Application

34. NoSQL
Domain Cloud Operations Application

35. Object Storage
Domain Cloud Operations Application

36. Non-Destructive
Updates
Domain Cloud Operations Application

37. Embrace
Eventual
Consistency
Domain Cloud Operations Application

38. Dev/Ops
Domain Cloud Operations Application

39. Continuous
Integration
Domain Cloud Operations Application

40. Continuous
Delivery
Domain Cloud Operations Application

41. Incremental
Rollouts
Domain Cloud Operations Application

42. Design
for
Failure
Domain Cloud Operations Application

43. Share
Nothing
Domain Cloud Operations Application

44. Logging
Domain Cloud Operations Application

45. Service
Discovery
Domain Cloud Operations Application

46. Ephemeral
Resources
Domain Cloud Operations Application

47. Avoid OS
Lock in
Domain Cloud Operations Application

48. Blameless
Post Mortem
Domain Cloud Operations Application

49. Google these:
“Always On: Assess, Design, Implements and Manage Continuous Availability”, Herbie Pearthree
“Top 9 rules for Cloud Applications”, Kyle Brown
Deep Dive

50. 20
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice and at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to
deliver any material, code or functionality.
Information about potential future products may not be incorporated into any contract.
The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of
multiprogramming in the user’s job stream, the I/O configuration,
the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
Brian O’Connell
@boc_tothefuture
linkedin.com/in/broconne