microservices software that fits in your head
play

Microservices: software that fits in your head Dan North @tastapod - PowerPoint PPT Presentation

Microservices: software that fits in your head Dan North @tastapod What is the point of software development? What is the purpose of software development? What is the purpose of software development? create business impact What is the


  1. Microservices: software that fits in your head Dan North @tastapod

  2. What is the point of software development?

  3. What is the purpose of software development?

  4. What is the purpose of software development? create business impact

  5. What is the purpose of software development? create positive business impact

  6. What is the goal of software development?

  7. What is the goal of software development? minimise lead time to business impact

  8. What is the goal of software development? sustainably minimise lead time to business impact

  9. The goal is not to produce software!

  10. produce

  11. produce production

  12. produce productive production

  13. productive ≠ effective

  14. Code is not the asset…

  15. Code is not the asset… Code is the cost!

  16. Code is not the asset… - writing code costs 
 Code is the cost!

  17. Code is not the asset… - writing code costs 
 - waiting for code costs 
 Code is the cost!

  18. Code is not the asset… - writing code costs 
 - waiting for code costs 
 - changing code costs 
 Code is the cost!

  19. Code is not the asset… - writing code costs 
 - waiting for code costs 
 - changing code costs 
 - understanding code costs Code is the cost!

  20. understanding code

  21. understanding code code I know

  22. understanding code code I know code everyone knows

  23. understanding code code I know code no-one knows! code everyone knows

  24. Code should be stabilised or killed off

  25. Code should be stabilised or killed off fast!

  26. Two complementary patterns

  27. Two complementary patterns Short Software Half-Life

  28. Two complementary patterns Short Software Half-Life Fits In My Head

  29. Short Software Half-Life

  30. Short Software Half-Life Design considerations

  31. Short Software Half-Life Design considerations - write discrete components 


  32. Short Software Half-Life Design considerations - write discrete components 
 - define component boundary 


  33. Short Software Half-Life Design considerations - write discrete components 
 - define component boundary 
 - define component purpose 


  34. Short Software Half-Life Design considerations - write discrete components 
 - define component boundary 
 - define component purpose 
 - define component responsibility

  35. Short Software Half-Life Stewardship considerations

  36. Short Software Half-Life Stewardship considerations - write component tests and docs 


  37. Short Software Half-Life Stewardship considerations - write component tests and docs 
 - optimise for replaceability 


  38. Short Software Half-Life Stewardship considerations - write component tests and docs 
 - optimise for replaceability 
 - expect to invest in stabilising 


  39. Short Software Half-Life Stewardship considerations - write component tests and docs 
 - optimise for replaceability 
 - expect to invest in stabilising 
 - build a stable team

  40. Fits In My Head

  41. Fits In My Head - multiple dimensions

  42. Fits In My Head - multiple dimensions - multiple scales

  43. Fits In My Head - multiple dimensions - multiple scales - “What would James do?”

  44. Fits In My Head - multiple dimensions - multiple scales - “What would James do?” Contextual Consistency

  45. Fits In My Head - multiple dimensions - multiple scales - “What would James do?” Contextual Consistency - agree guiding principles

  46. Fits In My Head - multiple dimensions - multiple scales - “What would James do?” Contextual Consistency - agree guiding principles - agree idioms

  47. Fits In My Head - multiple dimensions - multiple scales - “What would James do?” Contextual Consistency - agree guiding principles - agree idioms - difference is data

  48. Fits In My Head - multiple dimensions - multiple scales - “What would James do?” Contextual Consistency - agree guiding principles - agree idioms - difference is data - familiarity ≠ simplicity

  49. Replaceable Component Architecture

  50. Replaceable Component Architecture sustainably…

  51. Replaceable Component Architecture sustainably…

  52. Replaceable Component Architecture sustainably…

  53. Replaceable Component Architecture sustainably…

  54. Replaceable Component Architecture sustainably…

  55. Replaceable Component Architecture sustainably…

  56. Replaceable Component Architecture sustainably… “little computers 
 passing messages”

  57. Replaceable Component Architecture sustainably… “little computers 
 passing messages” — Alan Kay

  58. Replaceable Component Architecture sustainably… “little computers passing messages” — Alan Kay

  59. Microservices can be a Replaceable Component Architecture

  60. Microservices can be a Replaceable Component Architecture - if you choose to optimise for replaceability and consistency 


  61. Microservices can be a Replaceable Component Architecture - if you choose to optimise for replaceability and consistency 
 - smaller is not necessarily better 


  62. Microservices can be a Replaceable Component Architecture - if you choose to optimise for replaceability and consistency 
 - smaller is not necessarily better 
 - more replaceable is better

  63. Kill code fearlessly!

  64. Kill code fearlessly! code I know code no-one knows! code everyone knows

  65. Kill code fearlessly! code I know code everyone knows

  66. Thank you! Dan North @tastapod http:/ /dannorth.net http:/ /leanpub.com/software-faster

Recommend


More recommend