Microservices War Stories

98bcb9a1d462d6ea907fade0d601ea04?s=47 Blithe Rocher
May 18, 2016
Technology
1
130

Microservices War Stories

OSCON 2016

98bcb9a1d462d6ea907fade0d601ea04?s=128

Blithe Rocher

May 18, 2016
Tweet

More Decks by Blithe Rocher

See All by Blithe Rocher
98bcb9a1d462d6ea907fade0d601ea04?s=48 blithe
1
140
98bcb9a1d462d6ea907fade0d601ea04?s=48 blithe
2
530
98bcb9a1d462d6ea907fade0d601ea04?s=48 blithe
0
73

Other Decks in Technology

See All in Technology
2102a6b8760bd6f57f672805723dd83a?s=48 line_developers_tw
0
1.4k
6ca998e3a07596f141597da0d2983ecc?s=48 0si43
2
260
A857277d74d4719f7f7751dca5ed553e?s=48 cmusudakeisuke
0
450
A35557d139d8d53246763a01ec847a3f?s=48 kichiemon
3
450
Ff98f59b09d38b46d177e9a12b77dad4?s=48 yksn
0
230
9a22d09f92d50fa3d2a16766d0ba52f8?s=48 fabpot
5
2.1k
9fbbe5d0b8e2ee1cdc3a576b55a2d63d?s=48 uzimaru0000
1
130
C786d7772602b488a7972c38c143f61c?s=48 con_mame
3
1.8k
B1cb2027702d893b0f3aa096258d4814?s=48 mr04vv
1
170
F274f2fd3531a606f0a5766c9052b5d8?s=48 miyamotok
0
590
94a40b2e94d694c8b0324114c13a35ef?s=48 makash
0
150
47982be7ff38d38f65eb179dbdfb24f5?s=48 katsuya414
1
390

Featured

See All Featured
E13c31390e0369fcd5972292ce0e7b92?s=48 jnunemaker
PRO
40
4.4k
11c84dff30266b907714802088852677?s=48 jasonvnalue
80
7.9k
2f5463832ccb768ccb4a1ca3607c27ef?s=48 jacobian
251
19k
A9179349dd2bdc67f377719f56d85656?s=48 garrettdimon
284
110k
78b475797a14c84799063c7cd073962f?s=48 holman
459
270k
78b475797a14c84799063c7cd073962f?s=48 holman
287
130k
Ded01cdab114abe4ec13511e4c25b9bb?s=48 andyhume
60
2.4k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
775
240k
433acaea1012b25d97ae66da9b998dad?s=48 malarkey
118
15k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
142
19k
7653c7c449918ff6542880a8c284f5e7?s=48 jponch
101
4.8k
Ba530e786553390f3fb271848485681c?s=48 3n
160
22k

Transcript

  1. Blithe Rocher OSCON May 18, 2016 ` MICROSERVICES WAR STORIES

  2. @BLITHE

  3. None

  4. MICROSERVICES So…

  5. A MONOLITH vs.

  6. MICROSERVICES

  7. WHY ARE MICROSERVICES SO POPULAR?

  8. INDEPENDENT DEPLOYMENT & SCALABILITY 1 REASON

  9. 1 REASON

  10. 1 REASON

  11. 1 REASON

  12. 1 REASON

  13. 1 REASON

  14. 1 REASON

  15. COMPARTMENTALIZE TEAMS & RESPONSIBILITIES 2 REASON

  16. TECHNICAL DESIGN FREEDOM 3 REASON

  17. FAULT TOLERANCE 4 REASON

  18. WHY ME?

  19. MAKING MISTAKES & LEARNING FROM THEM Experience

  20. STORY TIME

  21. SUPPORTING NEW CONTENT TYPE 1 STORY Story

  22. STORY: Supporting New Content Type

  23. STORY: Supporting New Content Type

  24. STORY: Supporting New Content Type

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

  26. STORY: Supporting New Content Type

  27. STORY: Supporting New Content Type

  28. STORY: Supporting New Content Type PROBLEM?

  29. STORY: Supporting New Content Type REMEDIES

  30. REMOVING A FEATURE FLAG 2 STORY Story

  31. UI Authorization Service STORY: Removing Feature Flags

  32. DELETING CODE Yay! STORY: Removing Feature Flags

  33. PROBLEM? STORY: Removing Feature Flags

  34. REMEDIES STORY: Removing Feature Flags

  35. TIGHTLY COUPLED SERVICES 3 STORY Story

  36. STORY: Tightly Coupled Services Microservice A Database Microservice B

  37. STORY: Tightly Coupled Services ALL THE WAY DOWN Headaches

  38. STORY: Tightly Coupled Services PRODUCTION

  39. STORY: Tightly Coupled Services Microservice A Database Microservice B

  40. STORY: Tightly Coupled Services Microservice A Database Microservice B

  41. STORY: Tightly Coupled Services Microservice A Database Microservice B

  42. STORY: Tightly Coupled Services DEVELOPMENT

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

    BE RUNNING

  44. STORY: Tightly Coupled Services Microservice A Database Microservice B

  45. STORY: Tightly Coupled Services AUTOMATED TESTING

  46. STORY: Tightly Coupled Services Microservice A Database Microservice B

  47. STORY: Tightly Coupled Services VCR RECORDING Solution?

  48. STORY: Tightly Coupled Services API Responses - 1992

  49. STORY: Tightly Coupled Services VCR GEM STORY: Tightly Coupled Services

  50. STORY: Tightly Coupled Services PROBLEM?

  51. STORY: Tightly Coupled Services REMEDIES

  52. STORY: Tightly Coupled Services

  53. STORY: Tightly Coupled Services

  54. STORY: Tightly Coupled Services BUNDLE EXEC RAKE TEST:REAL

  55. STORY: Tightly Coupled Services BUNDLE EXEC RAKE TEST:MOCK

  56. STRING VS INTEGER 4 STORY Story

  57. STORY: String vs. Integer

  58. STORY: String vs. Integer

  59. STORY: String vs. Integer

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

  61. STORY: String vs. Integer

  62. STORY: String vs. Integer

  63. STORY: String vs. Integer

  64. STORY: String vs. Integer

  65. STORY: String vs. Integer

  66. STORY: String vs. Integer

  67. STORY: String vs. Integer

  68. STORY: String vs. Integer

  69. PROBLEM? STORY: String vs. Integer

  70. REMEDIES STORY: String vs. Integer

  71. SUMMARY & TAKE AWAYS

  72. THANKS! Questions? @Blithe

  73. None