Downloaded 22 times
Uploaded byMozaic Works
James Lewis: Microservices - Systems That Are #neverdone at I T.A.K.E. Unconference 2015
This document discusses techniques for crafting microservices software. It suggests applying old techniques like SRP, YAGNI and TDD, as well as new techniques like consumer-driven contracts, semantic monitoring, semantic versioning, and testing services in production. While the future presents challenges, these techniques can help build well-crafted software that delivers steady value by deploying services independently and evolving them through "conversational change". The document encourages software developers to thoughtfully apply these techniques and continue honing their craft.
More Related Content
Similar to James Lewis: Microservices - Systems That Are #neverdone at I T.A.K.E. Unconference 2015
James Lewis: Microservices - Systems That Are #neverdone at I T.A.K.E. Unconference 2015
- 1. 1 never done building systemsthat are jalewis@thoughtworks.com @boicy
- 2.
- 3. 3 the future isscary
- 4. 4 "ever accelerating progressof technology and changes in the mode of human life, which gives the appearance of approaching some essential singularity in the history of the race beyond which human affairs, as we know them, could not continue” John von Neumann, as recorded by Ulam, 1958
- 5. 5 “Around the world,laboring women produce forty-five thousand babies a day, representing 1023 MIPS of processing power. Also around the world, fab lines casually churn out thirty million microprocessors a day, representing 1023 MIPS. In another ten months, most of the MIPS being added to the solar system will be machine-hosted for the first time”
- 6.
- 7. 7 “Self-Driving Trucks AreGoing to Hit Us Like a Human-Driven Truck” https://medium.com/basic-income/self-driving-trucks-are-going-to-hit-us-like-a-human-driven-truck-b8507d9c5961 source: Morgan Stanley This is where we’re at and this is what we face as we look towards a quickly approaching horizon of over 3 million unemployed truckers and millions more unemployed service industry workers in small towns all over the country dependent on truckers as consumers of their services.
- 8. “If you aren’tworried about strong AI within the next 5-10 years then you aren’t working closely enough with AI teams” (paraphrasing Elon Musk) 8
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. HOW WE DESIGNSOFTWARE IS CHANGING 14
- 19.
- 20. 16 “the first post-devopsarchitectural style” Neal Ford
- 21.
- 22.
- 23. 19 never done Incomplete adjective not havingall the necessary or appropriate parts
- 24. 19 never done Incomplete adjective not havingall the necessary or appropriate parts
- 25.
- 26. 20 “This, milord, ismy family's axe. We have owned it for almost nine hundred years, see. Of course, sometimes it needed a new blade. And sometimes it has required a new handle, new designs on the metalwork, a little refreshing of the ornamentation . . . but is this not the nine hundred-year-old axe of my family? And because it has changed gently over time, it is still a pretty good axe, y'know. Pretty good.” never done
- 27. 21 microservices should be: cheapto replace and should allow us to go as “fast as possible”? quick to scale able to withstand failure
- 28.
- 29. 22 Hardest things todo: End-to-end testing
- 30. 22 Hardest things todo: End-to-end testing Independent deployment
- 31. 22 Hardest things todo: End-to-end testing Independent deployment Service versioning / evolution
- 32. TESTING MICROSERVICES ISHARD 23 Service A Service Large Medium Small
- 33. TESTING MICROSERVICES ISHARD 23 Service A Service Large Medium Small
- 34. Service Stub TESTING MICROSERVICES ISHARD 23 Service A Large Medium Small
- 35. INTEGRATING MICROSERVICES ISHARD 24
- 36. INTEGRATING MICROSERVICES ISHARD 24 Integration Test
- 37. INTEGRATING MICROSERVICES ISHARD 24 Integration Test Prod…
- 38. INTEGRATING MICROSERVICES ISHARD 24 Integration Test Prod…
- 39. INTEGRATING MICROSERVICES ISHARD 24 Integration Test Prod…
- 40. INTEGRATING MICROSERVICES ISHARD 24 Integration Test Prod…
- 41.
- 42. 26 WHAT DOES THISMEAN FOR THE CRAFT OF SOFTWARE DEVELOPMENT?
- 43.
- 44.
- 45. 29 well crafted software steadilyadding value
- 46.
- 47. 31 Nat Pryce Steve Freeman DanNorth Sydney ‘Hoppalong’ Redelinghuys Jim Webber Ian Robinson Ivan Moore Liz Keogh Simon Stewart Jez Humble Dave Farley Jay Fields Dan Worthington-Bodart Joe Walnes
- 48. 31 Nat Pryce Steve Freeman DanNorth Sydney ‘Hoppalong’ Redelinghuys Jim Webber Ian Robinson Ivan Moore Liz Keogh Simon Stewart Jez Humble Dave Farley Jay Fields Dan Worthington-Bodart Joe Walnes APPEAL TO AUTHORITY WARNING!
- 49. 32 TW is anXP shop
- 50.
- 51. 34 does this stillmake sense?
- 52.
- 53. 35 Gemini Project, Rogallowing Source: wikipedia.org
- 54.
- 55. 37 Gemini Project, Rogallowing Source: wikipedia.org it’s turtles all the way down
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62. 4444 Build out services as youneed them
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70. 52 (incidentally, if youwere playing the Conway’s law lottery, that’s when you number came up)
- 71.
- 72.
- 73. 55 git clone https://github.com/boicy/service-template (notethis doesn’t exist)
- 74.
- 75. 57 DRY within services duplicationbetween services
- 76.
- 77. 59 “The London school ofTest Driven Development” Mike Feathers
- 78. 60 should we writeunit tests?
- 79. 61 Nat Pryce Steve Freeman DanNorth Sydney ‘Hoppalong’ Redelinghuys Jim Webber Ian Robinson Ivan Moore Liz Keogh Simon Stewart Jez Humble Dave Farley Jay Fields Dan Worthington-Bodart Joe Walnes
- 80.
- 81. should we writeunit tests? 63 personally I think it’s more important than *ever*
- 82.
- 83. 65 a class shouldbe no bigger than my head
- 84.
- 85.
- 86.
- 87.
- 88. 70 SRP a service should beno bigger than my head
- 89.
- 90.
- 91.
- 92.
- 93.
- 94. 75 cron, python, boto,pydot, graphviz
- 95. 75 cron, python, boto,pydot, graphviz
- 96. 76 cron, python, boto,pydot, graphviz Do the simplest thing possible
- 97. 77 but what abouttesting and deployment
- 98.
- 99.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115. 85 0 10 2030 40 50 60 70 80 90 100 0 0.05 0.10 0.15 0.20 0.25 0.30 m Probability of weekly interaction x x x x x xxxx xx xx x x x x x x x x The effect of distance on communication
- 116. 86 Low change rate inter-companyintegration High stability Semantic Versioning Contract Testing Tolerant Reader “Conversational change”
- 117. 87 higher change rate inter-teamintegration lower stability Semantic Versioning Contract Testing Tolerant Reader “Conversational change”
- 118. 88 highest change rate intra-team loweststability Semantic Versioning Contract Testing Tolerant Reader “Conversational change”
- 119.
- 120.
- 121. 91 the future isscary
- 122. we are learninghow to: Craft my families axe Deploy microservices independently Test microservices in isolation Test microservices in production
- 123. 93 the future isbright
- 124. 94 we have oldtechniques that apply: SRP GRASP YAGNI KISS TDD DRY
- 125. and new techniquesto apply: Consumer Driven Contracts Semantic Monitoring Semantic Versioning Testing in Production
- 126.
- 127. 96 software craftsmanship isaround the code too
- 128. 96 software craftsmanship isaround the code too chunk up and think about the “gaps”
- 129. 96 software craftsmanship isaround the code too chunk up and think about the “gaps” and
- 130. 96 software craftsmanship isaround the code too chunk up and think about the “gaps” do the simplest thing possible and
- 131.
- 132. 98 Go forth andcraft software jalewis@thoughtworks.com @boicy
- 133. 98 Go forth andcraft software jalewis@thoughtworks.com @boicy Thanks! Go forth and craft software drink beer!
- 134. 99 I, for one,welcome our new overlords