Cloud Patterns

Transcript

1. DevOps Culture Yury Niño Roa Cloud Patterns
2. Performance, resilience, and power consumption are interdependent key system design factors. An increase in resilience (e.g., though redundancy) can result in higher performance and in higher power consumption (as more hardware). Saurabh Hukerikar Christian Engelmann
3. A design pattern describes a generalizable solution to a recurring problem that occurs within a well-defined context. Saurabh Hukerikar Christian Engelmann
5. Cloud Patterns Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience
6. Availability Patterns • Health Endpoint Monitoring • Queue-Based Load Leveling • Throttling Dulle Griet by Pieter Bruegel
7. Health Endpoint Monitoring
8. Queue-Based Load Leveling
9. Throttling
10. Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience Cloud Patterns
11. Data Management • Cache-Aside • CQRS • Event Sourcing • Index Table • Materialized View • Sharding • Static Content Hosting • Valet Key
12. Cache-Aside
13. CQRS - Command and Query Responsibility Segregation
14. Event Sourcing
15. Index Table
16. Materialized View
17. Sharding
18. Static Content Hosting
19. Valet Key
20. Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience Cloud Patterns
21. Design & Implementation • Ambassador • Anti-Corruption Layer. • Backends for Frontends. • CQRS. • Compute Resource Consolidation. • External Configuration Store.
22. Design & Implementation • Gateway Aggregation • Gateway Offloading. • Gateway Routing. • Leader Election. • Pipeline & Filters. • Sidecar. • Static Content Hosting. • Strangler.
23. Ambassador
24. Anti-corruption Layer
25. Backends for Frontends
26. CQRS - Command and Query Responsibility Segregation
27. Compute Resource Consolidation
28. External Configuration Store
29. Gateway Aggregation
30. Gateway Offloading
31. Gateway Routing
32. Leader Election
33. Pipe and Filters
34. Sidecar
35. Static Content Hosting
36. Strangler
37. Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience Cloud Patterns
38. Messaging • Asynchronous Request-Reply • Claim Check • Choreography • Competing Consumers • Pipes and Filters • Priority Queue • Publisher-Subscriber • Queue-Based Load Leveling • Scheduler Agent Supervisor. Dulle Griet by Pieter Bruegel
39. Asynchronous Request-Reply
40. Claim Check
41. Choreography
42. Competing Consumers
43. Priority Queue
44. Publisher-Subscriber
45. Queue-Based Load Leveling
46. Scheduler Agent Supervisor
47. Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience Cloud Patterns
48. Management & Monitoring • Ambassador • Anti-Corruption Layer • External Configuration Store • Gateway Aggregation • Gateway Offloading • Gateway Routing • Health Endpoint • Sidecar • Strangler
49. Ambassador
50. Anti-corruption Layer
51. External Configuration Store
52. Gateway Aggregation
53. Gateway Offloading
54. Gateway Routing
55. Health Endpoint Monitoring
56. Sidecar
57. Strangler
58. Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience Cloud Patterns
59. Performance & Scalability • Cache-Aside • Choreography • CQRS • Event Sourcing • Index Table
60. Performance & Scalability • Materialized View • Priority Queue • Queue-Based Load Leveling • Sharding • Static Content Hosting • Throttling
61. Cache-Aside
62. Choreography
63. CQRS - Command and Query Responsibility Segregation
64. Event Sourcing
65. Index Table
66. Materialized View
67. Priority Queue
68. Sharding
69. Static Content Hosting
70. Throthing
71. Availability Data Management Design & Implementation Messaging Management & Monitoring Performance & Scalability Security Resilience Cloud Patterns
72. Resilience Patterns • Circuit Breaker • Bulkhead • Health Endpoint • Leader Election • Retry • Elastic Load Balancer
73. If we accept that failure is impossible to avoid completely, it becomes sensible to force failure and observe how our system responds to it as a planned exercise. It’s better to have a system fail for the first time while an entire team is watching and ready to take action, than at 3 a.m. when a system alert wakes up an on-call engineer.
74. Circuit Breaker
75. Bulkhead
76. Health Endpoint Monitoring
77. CQRS - Command and Query Responsibility Segregation
78. Leader Election
79. Valet Key
80. Valet Key