Microservices War Stories

Transcript

1. 1.

   Blithe Rocher OSCON May 18, 2016 ` MICROSERVICES WAR STORIES

2. 2.

   @BLITHE

3. 3.

   None
4. 4.

   MICROSERVICES So…

5. 5.

   A MONOLITH vs.

6. 6.

   MICROSERVICES

7. 7.

   WHY ARE MICROSERVICES SO POPULAR?

8. 8.

   INDEPENDENT DEPLOYMENT & SCALABILITY 1 REASON

9. 9.

   1 REASON

10. 10.

    1 REASON

11. 11.

    1 REASON

12. 12.

    1 REASON

13. 13.

    1 REASON

14. 14.

    1 REASON

15. 15.

    COMPARTMENTALIZE TEAMS & RESPONSIBILITIES 2 REASON

16. 16.

    TECHNICAL DESIGN FREEDOM 3 REASON

17. 17.

    FAULT TOLERANCE 4 REASON

18. 18.

    WHY ME?

19. 19.

    MAKING MISTAKES & LEARNING FROM THEM Experience

20. 20.

    STORY TIME

21. 21.

    SUPPORTING NEW CONTENT TYPE 1 STORY Story

22. 22.

    STORY: Supporting New Content Type

23. 23.

    STORY: Supporting New Content Type

24. 24.

    STORY: Supporting New Content Type

25. 25.

    CONTENT-TYPE: TEXT/HTML ☹ STORY: Supporting New Content Type

26. 26.

    STORY: Supporting New Content Type

27. 27.

    STORY: Supporting New Content Type

28. 28.

    STORY: Supporting New Content Type PROBLEM?

29. 29.

    STORY: Supporting New Content Type REMEDIES

30. 30.

    REMOVING A FEATURE FLAG 2 STORY Story

31. 31.

    UI Authorization Service STORY: Removing Feature Flags

32. 32.

    DELETING CODE Yay! STORY: Removing Feature Flags

33. 33.

    PROBLEM? STORY: Removing Feature Flags

34. 34.

    REMEDIES STORY: Removing Feature Flags

35. 35.

    TIGHTLY COUPLED SERVICES 3 STORY Story

36. 36.

    STORY: Tightly Coupled Services Microservice A Database Microservice B

37. 37.

    STORY: Tightly Coupled Services ALL THE WAY DOWN Headaches

38. 38.

    STORY: Tightly Coupled Services PRODUCTION

39. 39.

    STORY: Tightly Coupled Services Microservice A Database Microservice B

40. 40.

    STORY: Tightly Coupled Services Microservice A Database Microservice B

41. 41.

    STORY: Tightly Coupled Services Microservice A Database Microservice B

42. 42.

    STORY: Tightly Coupled Services DEVELOPMENT

43. 43.

    STORY: Tightly Coupled Services SERVICES NOT ISOLATED, ALL NEED TO

    BE RUNNING
44. 44.

    STORY: Tightly Coupled Services Microservice A Database Microservice B

45. 45.

    STORY: Tightly Coupled Services AUTOMATED TESTING

46. 46.

    STORY: Tightly Coupled Services Microservice A Database Microservice B

47. 47.

    STORY: Tightly Coupled Services VCR RECORDING Solution?

48. 48.

    STORY: Tightly Coupled Services API Responses - 1992

49. 49.

    STORY: Tightly Coupled Services VCR GEM STORY: Tightly Coupled Services

50. 50.

    STORY: Tightly Coupled Services PROBLEM?

51. 51.

    STORY: Tightly Coupled Services REMEDIES

52. 52.

    STORY: Tightly Coupled Services

53. 53.

    STORY: Tightly Coupled Services

54. 54.

    STORY: Tightly Coupled Services BUNDLE EXEC RAKE TEST:REAL

55. 55.

    STORY: Tightly Coupled Services BUNDLE EXEC RAKE TEST:MOCK

56. 56.

    STRING VS INTEGER 4 STORY Story

57. 57.

    STORY: String vs. Integer

58. 58.

    STORY: String vs. Integer

59. 59.

    STORY: String vs. Integer

60. 60.

    ONE ENDPOINT TO RULE THEM ALL STORY: String vs. Integer

61. 61.

    STORY: String vs. Integer

62. 62.

    STORY: String vs. Integer

63. 63.

    STORY: String vs. Integer

64. 64.

    STORY: String vs. Integer

65. 65.

    STORY: String vs. Integer

66. 66.

    STORY: String vs. Integer

67. 67.

    STORY: String vs. Integer

68. 68.

    STORY: String vs. Integer

69. 69.

    PROBLEM? STORY: String vs. Integer

70. 70.

    REMEDIES STORY: String vs. Integer

71. 71.

    SUMMARY & TAKE AWAYS

72. 72.

    THANKS! Questions? @Blithe

73. 73.

    None