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!
Citation preview
1. Practical Considerations Of Microservices Sam Newman YOW
2013
2. @samnewman 3. Were Hiring!@samnewman 4. @samnewman 5.
@samnewman 6. @samnewman 7. @samnewman 8. @samnewman 9. @samnewman
10. @samnewman 11. @samnewman 12. @samnewman 13. Web ShopShopping
CartRegistrationCatalogFinanceCustomer@samnewman 14. REST over
HTTP@samnewman 15. REST over HTTP@samnewman 16. REST over HTTP>
1000 lines of code@samnewman 17. @samnewman 18. @samnewman 19.
V1@samnewman 20. V2@samnewman 21. V2@samnewman 22. Go RubyNodeJS
Java@samnewman 23. Go RubyNodeJS Clojure!@samnewman 24. Go
RubyNodeJS Clojure!@samnewman 25. @samnewman 26. @samnewman 27.
@samnewman 28. @samnewman 29.
http://www.ickr.com/photos/booleansplit/4005320314/Standardised@samnewman
30. http://www.ickr.com/photos/booleansplit/4005320314/Free For All
Standardisedhttp://www.ickr.com/photos/murplejane/3097926093/@samnewman
31. http://www.ickr.com/photos/booleansplit/4005320314/Free For All
StandardisedConsistency
http://www.ickr.com/photos/murplejane/3097926093/@samnewman 32.
http://www.ickr.com/photos/booleansplit/4005320314/Free For All
StandardisedConsistency
Safetyhttp://www.ickr.com/photos/murplejane/3097926093/@samnewman
33. http://www.ickr.com/photos/booleansplit/4005320314/Autonomy
Free For All StandardisedConsistency
Safetyhttp://www.ickr.com/photos/murplejane/3097926093/@samnewman
34. http://www.ickr.com/photos/booleansplit/4005320314/React
Autonomy Free For AllStandardisedConsistency
Safetyhttp://www.ickr.com/photos/murplejane/3097926093/@samnewman
35. http://bit.ly/1aJhJ0m@samnewman 36.
http://bit.ly/1aJhJ0mResponsiveness@samnewman 37.
http://bit.ly/1aJhJ0mResponsivenessEfciency@samnewman 38.
@samnewman 39. A paradox has a resolution, not a solution - Xiao
Guo@samnewman 40. @samnewman 41. Standardisation@samnewman 42.
StandardisationFree For All@samnewman 43. StandardisationFree For
All@samnewman 44. StandardisationFree For All@samnewman 45.
Standardisation ???Free For All@samnewman 46. Where To
Standardise?@samnewman 47. 2013 Electronic Arts Inc.@samnewman 48.
@samnewman 49. Interfaces@samnewman 50.
MonitoringInterfaces@samnewman 51. MonitoringInterfacesDeployment
@samnewman 52. Architectural Saftey @samnewman 53. @samnewman 54.
Free For All @samnewman 55. StandardisationFree For All @samnewman
56. Standardisation TIP: Standardise in the gaps between services -
be exible about what happens inside the boxesFree For All
@samnewman 57. Interfaces@samnewman 58. @samnewman 59. @samnewman
60. @samnewman 61. Coupling Is Bad@samnewman 62. Integration Styles
An Evolutionary ViewData OrientedProcedure OrientedDocument
OrientedResource Oriented@samnewman 63. Integration Styles An
Evolutionary ViewData OrientedProcedure OrientedDocument
OrientedResource Oriented@samnewman 64. Integration Styles An
Evolutionary View TIP: Avoid RPC-mechanisms or shared serialisation
Procedure Document Resource Data protocols to avoid coupling
Oriented OrientedOrientedOriented@samnewman 65.
http://www.ickr.com/photos/mikecogh/4472054494/@samnewman 66.
http://www.ickr.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 70. PaymentInventory@samnewman 71.
PaymentInventory@samnewman 72. Because CAP Theorem@samnewman 73.
Because CAP Theorem TIP: Avoid distributed transactions if at all
possible@samnewman 74. Monitoring@samnewman 75. @samnewman 76.
@samnewman http://www.ickr.com/photos/kalexanderson/5421517469/ 77.
@samnewman http://www.ickr.com/photos/kalexanderson/5421517469/ 78.
@samnewman http://www.ickr.com/photos/kalexanderson/5421517469/ 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 TimeResponse
TimeResponse Time@samnewman 94. Response TimeResponse TimeResponse
Time@samnewman 95. Response TimeResponse TimeResponse
Time@samnewman 96. nsclient++ collectdGraphite@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: 123ID: 123ID: 123@samnewman 109. ID: 123ID: 123ID: 123
TIP: Use correlation IDs to track down nasty bugs @samnewman 110.
Deployment@samnewman 111. @samnewman 112. @samnewman 113.
@samnewman 114. !@samnewman 115. ! !@samnewman 116. ! ! !
@samnewman 117. !TIP: Abstract out underlying platform dierences to
provide a uniform deployment mechanism!! @samnewman 118. @samnewman
119. $ fab deploy def deploy(): # run things local(cp) @samnewman
120. Fast FeedbackDevQAProductionMore Condence @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 126. " Customer
Service V1 127. " " Customer Service V1 128. " " " Customer Service
V1 129. " " " " Customer Service V1 130. " " " " Customer Service
V1 131. FinanceCustomer Service V1 132. FinanceCustomer Service
V1Customer Service v2 133. FinanceCustomer Service
V1FinanceCustomer Service v2 134. Integration TestFinanceCustomer
Service v2 135. FinanceCustomer Service v2 136. FinanceConsumer
written testCustomer Service v2 137. FinanceConsumer written
testCustomer Service v2 138. FinanceCustomer Service v2TIP:
Consumer Driven Tests to catch breaking changesConsumer written
test 139. PendingProd 140. PendingProd 141. PendingProd 142.
PendingProd 143. PendingProd 144. PendingProdTIP: Dont let changes
build up - release as soon as you can, and preferably one at a
time! 145. Architectural Safety@samnewman 146. @samnewman 147.
@samnewman 148. @samnewman 149. @samnewman 150.
http://www.flickr.com/photos/louish/5611657857/@samnewman 151.
@samnewman 152. TIP: Use timeouts, circuit breakers and bulk-heads
to avoid cascading failure@samnewman 153. Special Service
Behaviour@samnewman 154. IntegrationSpecial Service
Behaviour@samnewman 155. IntegrationSpecial Service
BehaviourDownstream@samnewman 156. IntegrationSpecial Service
BehaviourMetricsDownstream@samnewman 157. IntegrationSpecial
Service BehaviourMetricsDownstream@samnewman 158.
IntegrationSpecial Service BehaviourMetricsDownstream@samnewman
159. IntegrationSpecial Service BehaviourMetricsTIP: Consider
Service Templates to make it easy to do the right thing!
Downstream@samnewman 160. TIP: Standardise in the gaps between
services - be exible 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 dierences 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: Dont 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 exible about what happens inside the
boxes@samnewman 165. TIP: Standardise in the gaps between services
- be exible about what happens inside the boxes@samnewman 166. TIP:
Standardise in the gaps between services - be exible about what
happens inside the boxesTIP: Dont 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 exible about what
happens inside the boxesTIP: Dont 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
ReleaseFrom Macro To Micro@samnewman 170. Designing For ! Rapid
ReleaseFrom Macro To
Microhttp://lanyrd.com/prole/samnewman/@samnewman 171.
Thanks!@samnewman [email protected]@samnewman
