Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Microservices War Stories

Blithe Rocher
May 18, 2016
Technology
1
180

Microservices War Stories

OSCON 2016

Blithe Rocher

May 18, 2016
Tweet

More Decks by Blithe Rocher

See All by Blithe Rocher
The Scientific Method of Troubleshooting
blithe
1
210
The Scientific Method of Troubleshooting
blithe
2
670
The Scientific Method of Troubleshooting
blithe
0
130

Other Decks in Technology

See All in Technology
Microsoft の SSE の現在地
skmkzyk
0
200
技術者はかっこいいものだ！！～キルラキルから学んだエンジニアの生き方～
masakiokuda
2
280
AZ 名とAZ ID の違いを 何度でも言うよ
miu_crescent
PRO
0
100
Cross Data Platforms Meetup LT 20250422
tarotaro0129
1
840
2025-04-14 Data & Analytics 井戸端会議 Multi tenant log platform with Iceberg
kamijin_fanta
0
140
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
5.4k
C++26アップデート 2025-03
faithandbrave
0
1.1k
AIエージェント開発手法と業務導入のプラクティス
ykosaka
9
2.4k
Mastraに入門してみた ~AWS CDKを添えて~
tsukuboshi
0
360
地味にいろいろあった！ 2025春のAmazon Bedrockアップデートおさらい
minorun365
PRO
2
520
3月のAWSアップデートを5分間でざっくりと！
kubomasataka
0
130
ワールドカフェI ／チューターを改良する / World Café I and Improving the Tutors
ks91
PRO
0
140

Featured

See All Featured
KATA
mclloyd
29
14k
Making Projects Easy
brettharned
116
6.1k
Faster Mobile Websites
deanohume
306
31k
Unsuck your backbone
ammeep
670
57k
Speed Design
sergeychernyshev
29
910
Mobile First: as difficult as doing things right
swwweet
223
9.6k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.8k
Large-scale JavaScript Application Architecture
addyosmani
512
110k
Building Adaptive Systems
keathley
41
2.5k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Why Our Code Smells
bkeepers
PRO
336
57k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
104
19k

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