Practical microservices - YOW 2013
•
21 likes•6,865 views
The deck for Practical Microservices as presented at YOW 2013 in Brisbane. Minor changes from the Melbourne event. Bonus point if you can spot the typo!
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Practical microservices - YOW 2013
Similar to Practical microservices - YOW 2013 (20)
More from Sam Newman
Recently uploaded
Recently uploaded (20)
Practical microservices - YOW 2013
- 1. Practical Considerations Of Microservices Sam Newman YOW 2013
- 2. @samnewman
- 4. @samnewman
- 5. @samnewman
- 6. @samnewman
- 7. @samnewman
- 8. @samnewman
- 9. @samnewman
- 10. @samnewman
- 11. @samnewman
- 12. @samnewman
- 16. REST over HTTP > 1000 lines of code @samnewman
- 17. @samnewman
- 18. @samnewman
- 19. V1 @samnewman
- 20. V2 @samnewman
- 21. V2 @samnewman
- 25. @samnewman
- 26. @samnewman
- 27. @samnewman
- 28. @samnewman
- 38. @samnewman
- 39. “A paradox has a resolution, not a solution” - Xiao Guo @samnewman
- 40. @samnewman
- 47. © 2013 Electronic Arts Inc. @samnewman
- 48. @samnewman
- 53. @samnewman
- 56. Standardisation TIP: Standardise in the gaps between services - be flexible about what happens inside the boxes Free For All @samnewman
- 58. @samnewman
- 59. @samnewman
- 60. @samnewman
- 62. Integration Styles An Evolutionary View Data Oriented Procedure Oriented Document Oriented Resource Oriented @samnewman
- 63. Integration Styles An Evolutionary View Data Oriented Procedure Oriented Document Oriented Resource Oriented @samnewman
- 64. Integration Styles An Evolutionary View TIP: Avoid RPC-mechanisms or shared serialisation Procedure Document Resource Data protocols to avoid coupling Oriented Oriented Oriented Oriented @samnewman
- 66. http://www.flickr.com/photos/mikecogh/4472054494/ TIP: Have one, two or maybe three ways of integrating, not 20 @samnewman
- 67. @samnewman
- 68. @samnewman
- 69. TIP: Pick some sensible conventions, and stick with them @samnewman
- 73. Because CAP Theorem TIP: Avoid distributed transactions if at all possible @samnewman
- 75. @samnewman
- 79. @samnewman
- 80. @samnewman
- 81. ??? @samnewman
- 82. You have to get *much* better at monitoring @samnewman
- 83. @samnewman
- 84. @samnewman
- 85. @samnewman
- 86. @samnewman
- 87. You are not a badass if you use an SSH Multiplexer @samnewman
- 88. @samnewman
- 89. @samnewman
- 90. @samnewman
- 91. @samnewman
- 92. @samnewman
- 93. Response Time Response Time Response Time @samnewman
- 94. Response Time Response Time Response Time @samnewman
- 95. Response Time Response Time Response Time @samnewman
- 97. @samnewman
- 98. @samnewman
- 99. TIP: Capture metrics, and logs, for each node, and aggregate them to get a rolled up picture @samnewman
- 100. @samnewman
- 101. @samnewman
- 102. @samnewman
- 103. TIP: Use synthetic transactions to test production systems @samnewman
- 104. @samnewman
- 105. @samnewman
- 106. @samnewman
- 107. ID: 123 @samnewman
- 108. ID: 123 ID: 123 ID: 123 @samnewman
- 109. ID: 123 ID: 123 ID: 123 TIP: Use correlation IDs to track down nasty bugs @samnewman
- 111. @samnewman
- 112. @samnewman
- 113. @samnewman
- 114. ! @samnewman
- 115. ! ! @samnewman
- 116. ! ! ! @samnewman
- 117. ! TIP: Abstract out underlying platform differences to provide a uniform deployment mechanism ! ! @samnewman
- 118. @samnewman
- 119. $ fab deploy def deploy(): # run things local(‘cp…’) @samnewman
- 121. fab deploy:dev def deploy(env): # run things local(‘cp…’) @samnewman
- 122. fab deploy:dev def deploy(env): # run things local(‘cp…’) @samnewman
- 123. prod:! nodes:! - ami_id: ami-4dad7424! size: t1.micro! credentials_name: us-east-ssh! aws_key_name : test! services: [hello_world]! apache:! security_groups: [ spicy-beef ]! puppet_module_directory : puppet! availability_zone: us-east-1a! puppet_manifest : apache.pp! type: phoenix.providers.aws_provider.AWSNodeDefinition! service_configurator: - ami_id: ami-4dad7424! phoenix.configurators.puppet_service_configurator.PuppetServiceConfigurator! size: t1.micro! connectivity:! credentials_name: us-east-ssh! - protocol: tcp! aws_key_name : test! ports: [ 80 ]! services: [hello_world]! allowed: [ WORLD ]! security_groups: [ spicy-beef ]! availability_zone: us-east-1b! hello_world:! type: phoenix.providers.aws_provider.AWSNodeDefinition! puppet_module_directory : puppet! - ami_id: ami-4dad7424! puppet_manifest : hello_world.pp! size: t1.micro! service_configurator: credentials_name: us-east-ssh! phoenix.configurators.puppet_service_configurator.PuppetServiceConfigurator! aws_key_name : test! connectivity:! services: [apache]! - protocol: tcp! type: phoenix.providers.aws_provider.AWSNodeDefinition! ports: [ 8080, 8081 ]! security_groups: [ spicy-beef ]! allowed: [ WORLD ]! ! ! ! node_provider:! mongo:! class_name: AWSNodeProvider! puppet_module_directory : puppet! public_api_key: {{ aws_public_api_key }}! puppet_manifest private_api_key: {{ aws_private_api_key }} : mongo.pp! service_configurator: phoenix.configurators.puppet_service_configurator.PuppetServiceConfigurator! connectivity:! - protocol: tcp! ports: [ 27017 ]! allowed: [ hello_world ] @samnewman
- 124. prod:! nodes:! - ami_id: ami-4dad7424! size: t1.micro! credentials_name: us-east-ssh! aws_key_name : test! services: [hello_world]! apache:! security_groups: [ spicy-beef ]! puppet_module_directory : puppet! availability_zone: us-east-1a! puppet_manifest : apache.pp! type: phoenix.providers.aws_provider.AWSNodeDefinition! service_configurator: - ami_id: ami-4dad7424! phoenix.configurators.puppet_service_configurator.PuppetServiceConfigurator! size: t1.micro! connectivity:! credentials_name: us-east-ssh! - protocol: tcp! aws_key_name : test! ports: [ 80 ]! services: [hello_world]! allowed: [ WORLD ]! security_groups: [ spicy-beef ]! availability_zone: us-east-1b! hello_world:! type: phoenix.providers.aws_provider.AWSNodeDefinition! puppet_module_directory : puppet! - ami_id: ami-4dad7424! puppet_manifest : hello_world.pp! size: t1.micro! service_configurator: credentials_name: us-east-ssh! phoenix.configurators.puppet_service_configurator.PuppetServiceConfigurator! aws_key_name : test! connectivity:! services: [apache]! - protocol: tcp! type: phoenix.providers.aws_provider.AWSNodeDefinition! ports: [ 8080, 8081 ]! security_groups: [ spicy-beef ]! allowed: [ WORLD ]! TIP: Have a single way of deploying services in any given environment ! ! ! node_provider:! mongo:! class_name: AWSNodeProvider! puppet_module_directory : puppet! public_api_key: {{ aws_public_api_key }}! puppet_manifest private_api_key: {{ aws_private_api_key }} : mongo.pp! service_configurator: phoenix.configurators.puppet_service_configurator.PuppetServiceConfigurator! connectivity:! - protocol: tcp! ports: [ 27017 ]! allowed: [ hello_world ] @samnewman
- 125. Customer Service V1
- 129. " " " " Customer Service V1
- 130. " " " " Customer Service V1
- 138. Finance Customer Service v2 TIP: Consumer Driven Tests to catch breaking changes Consumer written test
- 139. Pending… Prod
- 140. Pending… Prod
- 141. Pending… Prod
- 142. Pending… Prod
- 143. Pending… Prod
- 144. Pending… Prod TIP: Don’t let changes build up - release as soon as you can, and preferably one at a time!
- 146. @samnewman
- 147. @samnewman
- 148. @samnewman
- 149. @samnewman
- 151. @samnewman
- 152. TIP: Use timeouts, circuit breakers and bulk-heads to avoid cascading failure @samnewman
- 159. Integration Special Service Behaviour Metrics TIP: Consider Service Templates to make it easy to do the right thing! Downstream @samnewman
- 160. TIP: Standardise in the gaps between services - be flexible about what happens inside the boxes TIP: Avoid RPC-mechanisms or shared serialisation protocols to avoid coupling TIP: Have one, two or maybe three ways of integrating, not 20 TIP: Pick some sensible conventions, and stick with them @samnewman
- 161. TIP: Capture metrics, and logs, for each node, and aggregate them to get a rolled up picture TIP: Use synthetic transactions to test production systems TIP: Avoid distributed transactions if at all possible TIP: Use correlation IDs to track down nasty bugs TIP: Abstract out underlying platform differences to provide a uniform deployment mechanism @samnewman
- 162. TIP: Have a single way of deploying services in any given environment TIP: Consumer Driven Tests to catch breaking changes TIP: Don’t let changes build up - release as soon as you can, and preferably one at a time! TIP: Use timeouts, circuit breakers and bulk-heads to avoid cascading failure TIP: Consider Service Templates to make it easy to do the right thing! @samnewman
- 163. @samnewman
- 164. TIP: Standardise in the gaps between services - be flexible about what happens inside the boxes @samnewman
- 165. TIP: Standardise in the gaps between services - be flexible about what happens inside the boxes @samnewman
- 166. TIP: Standardise in the gaps between services - be flexible about what happens inside the boxes TIP: Don’t let changes build up - release as soon as you can, and preferably one at a time! @samnewman
- 167. TIP: Standardise in the gaps between services - be flexible about what happens inside the boxes TIP: Don’t let changes build up - release as soon as you can, and preferably one at a time! @samnewman
- 168. Designing For ! Rapid Release @samnewman
- 169. Designing For ! Rapid Release From Macro To Micro @samnewman
- 170. Designing For ! Rapid Release From Macro To Micro http://lanyrd.com/profile/samnewman/ @samnewman