Linux Conf Australia 2016 - Cloud Anti-Patterns

The value of embracing microservices, containers, and continuous delivery is powerful only when brought together in logical, scalable, and portable ways. When used incorrectly it’s increasingly easy to make things much worse for you and your team, and do it at scale.

For example, while microservices can be used to effectively isolate functionality, increase the speed of delivery, and help scale your team it can also be a way to inefficiently duplicate functionality and create single points of failure.

I’ll share anti-patterns and corresponding best practices based on my experience building application infrastructure and platforms, as well as the applications which are deployed to them.

Transcript

1. CLOUD ANTI-PATTERNS > Twitter @caseywest > Email casey@geeknest.com > Web http://caseywest.com > Days since I last used that joke zero 1 — @caseywest
2. THANKS A LOT, PIVOTAL 2 — @caseywest
3. THIS TALK IS MORE LIKE… 3 — @caseywest
4. THE FIVE STAGES OF CLOUD-NATIVE 1. Denial 2. Anger 3. Bargaining 4. Depression 5. Acceptance 4 — @caseywest
5. HAVE A SEAT ON THE COUCH 5 — @caseywest
6. WHATEVER MAKES YOU COMFORTABLE 6 — @caseywest
7. NOW FOR SOME BASIC GROUND RULES 7 — @caseywest
8. RULES WE WILL TALK ABOUT YOUR DELIVERY PIPELINE 8 — @caseywest
9. RULES WE WILL TALK ABOUT YOUR ARCHITECTURE 9 — @caseywest
10. RULES WE WILL TALK ABOUT YOUR AUTOMATION 10 — @caseywest
11. ⏰ 11 — @caseywest
12. "DEPLOYING MY APPS TO 'THE CLOUD' IS PAINTFUL. WHY?" 12 — @caseywest
13. DENIAL 13 — @caseywest
14. DENIAL CONTAINERS ARE JUST LIKE TINY VIRTUAL MACHINES 14 — @caseywest
15. DENIAL WE DON'T NEED TO AUTOMATE CONTINUOUS DELIVERY 15 — @caseywest
16. DENIAL NOT AUTOMATING CONTINUOUS DELIVERY 16 — @caseywest
17. ANGER 17 — @caseywest
18. ANGER WORKS ON MY MACHINE 18 — @caseywest
19. ANGER DEV IS JUST #YOLO-ING SHIT TO PRODUCTION 19 — @caseywest
20. BARGAINING 20 — @caseywest
21. BARGAINING WE CRAMMED THIS MONOLITH INTO A CONTAINER AND CALLED IT A MICROSERVICE 21 — @caseywest
22. BARGAINING "BI-MODAL IT" 22 — @caseywest
23. BARGAINING WHAT IF WE CREATE "MICROSERVICES" THAT ALL TALK TO THE SAME DATA SOURCE? 23 — @caseywest
24. DEPRESSION 24 — @caseywest
25. DEPRESSION WE MADE 200 MICROSERVICES AND FORGOT TO SET UP JENKINS 25 — @caseywest
26. DEPRESSION WE HAVE AN AUTOMATED BUILD PIPELINE BUT RELEASE TWICE A YEAR 26 — @caseywest
27. ACCEPTANCE 27 — @caseywest
28. ACCEPTANCE ALL SOFTWARE SUCKS 28 — @caseywest
29. ACCEPTANCE RESPECT CAP THEOREM 29 — @caseywest
30. ACCEPTANCE RESPECT CONWAY'S LAW 30 — @caseywest
31. ACCEPTANCE SMALL BATCH SIZE WORKS FOR REPLATFORMING, TOO 31 — @caseywest
32. ACCEPTANCE AUTOMATE EVERYTHING 32 — @caseywest
33. ⏰'S UP 33 — @caseywest
34. WHAT HAVE WE LEARNED? 34 — @caseywest
35. OPERABILITY IS 1. MICROSERVICES ARCHITECTURE 2. DEVOPS CULTURE 3. CONTINUOUS DELIVERY PICK THREE 35 — @caseywest
36. THANK YOU QUESTIONS? 36 — @caseywest
37. @CASEYWEST LET'S BE FRIENDS ! 37 — @caseywest