Uploaded byRenan Martins
Testing Microservices Architectures
The document explores microservices architectures, emphasizing their autonomous nature and the ability to change and deploy independently. It outlines key benefits such as technology heterogeneity, resilience, and ease of deployment, as well as testing strategies like unit, integration, and contract testing. Additionally, it discusses approaches to testing in production, including canary releases and the importance of fast recovery from defects.
More Related Content
Similar to Testing Microservices Architectures
Testing Microservices Architectures
- 1.
- 2. DEFINITION 2 “Micro services aresmall, autonomous services that work together"
- 3. SMALL 3 Focused on DoingOne Thing Well
- 4. AUTONOMOUS 4 Need to beable to change independently of each other, and be deployed by themselves without requiring consumers to change.
- 5. AM I DOINGIT RIGHT? 5 Can you make a change to a service and deploy it by itself without changing anything else?
- 6. 6 KEY BENEFITS OF MICROSERVICES ARCHITECTURES
- 7. TECHNOLOGY HETEROGENEITY 7 The righttool for each job! POSTS <<ruby>> FRIENDS <<golang>> PICTURES <<java>> <<Document Store>> <<graph DB>> <<Blob Store>>
- 8. RESILIENCE 8 We can buildsystems that handle the total failure of services and degrade functionality accordingly
- 9.
- 10. EASE OF DEPLOYMENT Deploysare faster, independent and problems can be isolated more easily
- 11. ORGANIZATIONAL ALIGNMENT INVOICING SERVICE INVENTORYSERVICE Smaller teams and smaller codebases Conway's Law
- 12.
- 13. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM
- 14. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM PROFILE MODULE
- 15. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM PROFILE MODULE
- 16. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM PROFILE MODULE HTTPS
- 17. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM PROFILE MODULE New Point of Sale HTTPS
- 18. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM PROFILE MODULE New Point of Sale HTTPS HTTP
- 19. COMPOSABILITY AND REPLACEABILITY MONOLITHICECOM SYSTEM PROFILE MODULE New Point of Sale HTTPS HTTP Affiliate Store HTTPS
- 20.
- 21. YOU MUST BETHIS TALL TO USE MICRO SERVICES http://martinfowler.com/bliki/MicroservicePrerequisites.html
- 22.
- 23.
- 24. 17 TEST AUTOMATION CLOSER TO THEUSER CLOSER TO THE DEVELOPER $$$ SLOWER / FEWER $ FASTER / MORE USER JOURNEY UI INTEGRATION UNIT Connection of UI tests to a persona like flow through the system Testing on the level of the users - incl. browser, network, databases, external systems, … Tests of multiple integrated method Tests of single methods without dependencies
- 25. 18 CODE PRODUCTION Unit, Integration,end to end tests, smoke tests, etc.. Consumers
- 26. 19 HOW DOES IT RELATETO MICRO SERVICES ARCHITECTURES ?
- 27. ANATOMY OF AMICROSERVICE 20http://martinfowler.com/articles/microservice-testing/
- 28. UNIT TESTING MICROSERVICES 21 Domain- We should focus on testing the behavior, observing changes on its state. Gateways, Resources and Persistence - We should focus on the interactions and collaboration (Mocks, test doubles) http://martinfowler.com/articles/microservice-testing/
- 29. INTEGRATION TESTS -PERSISTENCE E GATEWAYS 22http://martinfowler.com/articles/microservice-testing/
- 30. COMPONENT TESTS -IN PROCESS 23http://martinfowler.com/articles/microservice-testing/
- 31. COMPONENT TESTS -OUT OF PROCESS 24http://martinfowler.com/articles/microservice-testing/
- 32. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 25 Mock your APIs for fast, robust and comprehensive testing mountebank - over the wire test doubles
- 33. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26
- 34. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26
- 35. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26 test
- 36. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26 test Configure the stubs
- 37. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26 test Configure the stubs
- 38. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26 test SMTP TCP Stub HTTP Configure the stubs
- 39. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26 test Your application SMTP TCP Stub HTTP Configure the stubs
- 40. COMPONENT TESTS -HOW TO SIMULATE EXTERNAL SERVICES? 26 test Your application SMTP TCP Stub HTTP Configure the stubs
- 41. COMPONENT TESTS -PROBLEMS WITH STUBS 27
- 42. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Your application Stub / Imposter Test
- 43. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving Your application Stub / Imposter Test
- 44. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving Your application Stub / Imposter Test
- 45. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving Your application Stub / Imposter Test Becomes invalid!
- 46. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving Your application Stub / Imposter Test Becomes invalid!
- 47. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving BECOMES INVALID! Your application Stub / Imposter Test Becomes invalid!
- 48. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving BECOMES INVALID! Your application Stub / Imposter Test Becomes invalid!
- 49. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving BECOMES INVALID! Your application Stub / Imposter Test Becomes invalid!
- 50. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving BECOMES INVALID! Your application Stub / Imposter Test Becomes invalid!
- 51. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving BECOMES INVALID! Your application Stub / Imposter Test Becomes invalid!
- 52. COMPONENT TESTS -PROBLEMS WITH STUBS 27 Service constantly evolving How frequently do you change your stubs? BECOMES INVALID! Your application Stub / Imposter Test Becomes invalid!
- 53.
- 54.
- 55.
- 56. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving Service'sContinuous Integration Pipeline
- 57. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving Service'sContinuous Integration Pipeline
- 58. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT Service'sContinuous Integration Pipeline
- 59. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION Service'sContinuous Integration Pipeline
- 60. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT Service'sContinuous Integration Pipeline
- 61. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 62. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 63. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 64. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 65. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 66. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 67. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 68. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Service'sContinuous Integration Pipeline
- 69. CONSUMER DRIVEN CONTRACTS 29 Service constantly evolving UNIT INTEGRATION COMPONENT CONTRACT Deploy! Service'sContinuous Integration Pipeline
- 70. CONSUMER DRIVEN CONTRACTS- IMPLEMENTATIONS 30 https://github.com/realestate-com-au/pact
- 71. END TO ENDTESTS - BLACK BOX 31
- 72. END TO ENDTESTS - BLACK BOX 31
- 73. END TO ENDTESTS - BLACK BOX 31 1 4 2 3 5 6 7 8
- 74. END TO ENDTESTS - BLACK BOX 31 1 4 2 3 5 6 7 8
- 75. END TO ENDTESTS - BLACK BOX 31 1 4 2 3 5 6 7 8
- 76. END TO ENDTESTS - BLACK BOX 31 1 4 2 3 5 6 7 8 GOOD LUCK!
- 77. END TO ENDTESTING MICRO SERVICES ARCHITECTURES 32 Avoid the need for end-to-end tests wherever possible
- 78. END TO ENDTESTING MICRO SERVICES ARCHITECTURES 33 Test User Journeys, not stories
- 79. END TO ENDTESTING MICRO SERVICES ARCHITECTURES 34 Make sure your end to end tests are independent of existing data
- 80. CI PIPELINE -QUICK FEEDBACK VS COST 35 UNIT INTEGRATION CONTRACT COMPONENT JOURNEYS
- 81. WE COVERED THEWHOLE PYRAMID. ARE WE DONE YET? 36
- 82. WE COVERED THEWHOLE PYRAMID. ARE WE DONE YET? 36 Nope.
- 83. WE COVERED THEWHOLE PYRAMID. ARE WE DONE YET? 36 Nope. Testing in production!
- 84. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT
- 85. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT
- 86. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT SERVICE V1
- 87. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT SERVICE V1
- 88. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT SERVICE V1 SERVICE V2
- 89. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT SERVICE V1 SERVICE V2
- 90. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT SERVICE V1 SERVICE V2
- 91. TESTING IN PRODUCTION 37 Deployvs Release BLUE GREEN DEPLOYMENT SERVICE V1 SERVICE V2
- 92.
- 93.
- 94.
- 95.
- 96.
- 97.
- 98.
- 99.
- 100.
- 101.
- 102. MEAN TIME TORECOVER 39 Tests are very important to reduce the amount of defects in our systems. However, it's important to acknowledge that bugs will always happen in production. How fast we can recover from them will help determining our success!
- 103.
- 104.