1. PRACTICALCONSIDERATIONSFOR MICRO SERVICESSam NewmanJavazone 2014, September 20141

2. 14 PRACTICAL TIPSFOR MICROSERVICESSam NewmanJavazone 2014, September 20142 3. YOU WONT BELIEVEWHAT THEY DO WITHMICROSERVICES INTHIS TALK!Sam NewmanJavazone 2014, September 20143 4. SEE WHAT JENNIFERLAWRENCE THINKSABOUT DISTRIBUTEDSYSTEMS!Sam NewmanJavazone 2014, September 20144 5. CustomerServiceAccountsReturnsInvoicingShippingInventory@javazone @samnewman 6. Focused around a businessdomainCustomerServiceAccountsReturnsInvoicingShippingInventory@javazone @samnewman 7. Focused around a businessdomainCustomerServiceTechnology Agnostic APIAccountsReturnsInvoicingShippingInventory@javazone @samnewman 8. Focused around a businessdomainCustomerServiceTechnology Agnostic APISmallAccountsReturnsInvoicingShippingInventory@javazone @samnewman 9. @javazone @samnewman 10. @javazone @samnewman 11. V1@javazone @samnewman 12. V2@javazone @samnewman 13. GoJavaNodeJSRuby@javazone @samnewman 14. GoNodeJSRubyClojure!@javazone @samnewman 15. @javazone @samnewman 16. @javazone @samnewman 17. @javazone @samnewman 18. @javazone @samnewman 19. Where To Standardise?@javazone @samnewman 20. @javazone @samnewman 2013 Electronic Arts Inc. 21. @javazone @samnewman 22. Interfaces@javazone @samnewman 23. InterfacesMonitoring@javazone @samnewman 24. InterfacesMonitoringDeployment & Testing@javazone @samnewman 25. Architectural Safety@javazone @samnewman 26. @javazone @samnewman 27. Free For All@javazone @samnewman 28. StandardisationFree For All@javazone @samnewman 29. StandardisationTIP 1 / 14: Standardise in the gaps between services -be flexible about what happens inside the boxesFree For All@javazone @samnewman 30. @javazone @samnewman 31. @javazone @samnewman 32. @javazone @samnewman 33. @javazone @samnewman 34. @javazone @samnewman 35. @javazone @samnewmanhttps://www.flickr.com/photos/garrymsmith/6108841070 36. AutonomyCommunication@javazone @samnewman 37. Team Ownership@javazone @samnewman 38. Team Ownership???@javazone @samnewman 39. Trusted Committer /Roving Custodian@javazone @samnewman 40. Trusted Committer /Roving Custodian???@javazone @samnewman 41. Trusted Committer /Roving Custodian???@javazone @samnewman 42. Trusted Committer /Roving Custodian???@javazone @samnewman 43. Trusted Committer /Roving Custodian???@javazone @samnewman 44. Trusted Committer /Roving Custodian???@javazone @samnewman 45. Trusted Committer /Roving CustodianTIP 2 / 14: Have a cle?a?r ?custodian model!@javazone @samnewman 46. Interfaces@javazone @samnewman 47. @javazone @samnewman 48. @javazone @samnewman 49. @javazone @samnewman 50. Coupling Is Bad@javazone @samnewman 51. Integration StylesAn Evolutionary ViewData Oriented ProcedureOrientedDocumentOrientedResourceOriented@javazone @samnewman 52. Integration StylesAn Evolutionary ViewData Oriented ProcedureOrientedDocumentOrientedResourceOriented@javazone @samnewman 53. Integration StylesAn Evolutionary ViewTIP 3 / 14: Avoid RPC-mechanisms or sharedserialisation protocols to avoid couplingData Oriented ProcedureOrientedDocumentOrientedResourceOriented@javazone @samnewman 54. Database@javazone @samnewman 55. Database@javazone @samnewman 56. Database@javazone @samnewman 57. Database@javazone @samnewman 58. Database@javazone @samnewman 59. Database@javazone @samnewman 60. Database@javazone @samnewman 61. Database Database@javazone @samnewman 62. Database Database@javazone @samnewman 63. TIP 4 / 14: Separate the databases before separating servicesDatabase Database@javazone @samnewman 64. The Customer Is Always Right@javazone @samnewman 65. @javazone @samnewman 66. @javazone @samnewman 67. TIP 5 / 14: Adopt a consumer first approach@javazone @samnewman 68. Monitoring@javazone @samnewman 69. @javazone @samnewman 70. http://www.flickr.com/photos/kalexanderson/5421517469/@javazone @samnewman 71. http://www.flickr.com/photos/kalexanderson/5421517469/@javazone @samnewman 72. @javazone @samnewman 73. @javazone @samnewman 74. ???@javazone @samnewman 75. You have to get *much*better at monitoring@javazone @samnewman 76. @javazone @samnewman 77. @javazone @samnewman 78. @javazone @samnewman 79. @javazone @samnewman 80. You are not a badass if youuse an SSH Multiplexer@javazone @samnewman 81. @javazone @samnewman 82. @javazone @samnewman 83. @javazone @samnewman 84. Response TimeResponse TimeResponse Time@javazone @samnewman 85. Response TimeResponse TimeResponse Time@javazone @samnewman 86. Response TimeResponse TimeResponse Time@javazone @samnewman 87. @javazone @samnewman 88. @javazone @samnewman 89. TIP 6 / 14: Capture metrics, and logs, for each node,and aggregate them to get a rolled up picture@javazone @samnewman 90. @javazone @samnewman 91. @javazone @samnewman 92. @javazone @samnewman 93. TIP 7 / 14: Use synthetic transactions to testproduction systems@javazone @samnewman 94. @javazone @samnewman 95. @javazone @samnewman 96. @javazone @samnewman 97. ID: 123@javazone @samnewman 98. ID: 123ID: 123ID: 123@javazone @samnewman 99. ID: 123TIP 8 / 14: Use correlation IDs to track down nasty bugsID: 123ID: 123@javazone @samnewman 100. Deployment@javazone @samnewman 101. @javazone @samnewman 102. @javazone @samnewman 103. @javazone @samnewman 104. !@javazone @samnewman 105. !!@javazone @samnewman 106. !!!@javazone @samnewman 107. @javazone @samnewman 108. @javazone @samnewman 109. @javazone @samnewman 110. TIP 9 / 14: Abstract out underlying platformdifferences to provide a uniform deploymentmechanism@javazone @samnewman 111. ShippingInventoryCustomerServiceAccountsReturnsInvoicing@javazone @samnewman 112. CustomerServiceAccountsReturnsInvoicingShippingInventory@javazone @samnewman 113. CustomerServiceAccountsReturnsInvoicingShippingInventory@javazone @samnewman 114. Inventory AccountsMountebankhttp://www.mbtest.org@javazone @samnewman 115. InventoryAccounts!StubMountebankhttp://www.mbtest.org@javazone @samnewman 116. ShippingInventoryCustomerServiceAccountsReturnsInvoicing@javazone @samnewman 117. ShippingInventoryCustomerServiceAccountsReturnsInvoicing@javazone @samnewman 118. ShippingInventoryCustomerServiceAccountsReturnsInvoicing@javazone @samnewman 119. ShippingInventoryCustomerServiceAccountsReturnsInvoicing@javazone @samnewman 120. ShippingInventoryCustomerServiceAccountsReturnsInvoicing@javazone @samnewman 121. @javazone @samnewman 122. Browsers@javazone @samnewman 123. TimingBrowsers@javazone @samnewman 124. Provisioning of EnvironmentsTimingBrowsers@javazone @samnewman 125. NetworksProvisioning of EnvironmentsTimingBrowsers@javazone @samnewman 126. DeploymentNetworksProvisioning of EnvironmentsTimingBrowsers@javazone @samnewman 127. DeploymentNetworksProvisioning of EnvironmentsTimingBrowsers Diagnosis@javazone @samnewman 128. CONSUMER-DRIVEN CONTRACTSShipping Inventory@javazone @samnewman 129. CONSUMER-DRIVEN CONTRACTSShipping InventoryExpectations@javazone @samnewman 130. CONSUMER-DRIVEN CONTRACTSShipping InventoryExpectations@javazone @samnewman 131. CONSUMER-DRIVEN CONTRACTSShipping InventoryExpectationsProd@javazone @samnewman 132. CONSUMER-DRIVEN CONTRACTSShipping InventoryExpectationsProd@javazone @samnewman 133. @javazone @samnewman 134. https://github.com/realestate-com-au/pact@javazone @samnewman 135. TIP 10 / 14: Consumer Driven Tests to catch breaking changeshttps://github.com/realestate-com-au/pact@javazone @samnewman 136. Pending Prod 137. Pending Prod 138. Pending Prod 139. Pending Prod 140. Pending Prod 141. Pending ProdTIP 11 / 14: Dont let changes build up - release assoon as you can, and preferably one at a time! 142. Architectural Safety@javazone @samnewman 143. @javazone @samnewman 144. @javazone @samnewman 145. @javazone @samnewman 146. @javazone @samnewman 147. http://www.flickr.com/photos/louish/5611657857/@javazone @samnewman 148. Connection Pool@javazone @samnewman 149. Connection Pool@javazone @samnewman 150. Connection Pool@javazone @samnewman 151. Connection Pool@javazone @samnewman 152. ConnectionPoolConnectionPool@javazone @samnewman 153. ConnectionPoolConnectionPool@javazone @samnewman 154. ConnectionPoolConnectionPool@javazone @samnewman 155. ConnectionPoolConnectionPool@javazone @samnewman 156. @javazone @samnewman 157. @javazone @samnewman 158. @javazone @samnewman 159. TIP 12 / 14: Use timeouts, circuit breakers and bulk-headsto avoid cascading failure@javazone @samnewman 160. Special Service Behaviour@javazone @samnewman 161. IntegrationSpecial Service Behaviour@javazone @samnewman 162. IntegrationSpecial Service BehaviourDownstream@javazone @samnewman 163. IntegrationSpecial Service BehaviourDownstreamMetrics@javazone @samnewman 164. IntegrationSpecial Service BehaviourDownstreamMetrics@javazone @samnewman 165. IntegrationSpecial Service BehaviourDownstreamMetrics@javazone @samnewman 166. IntegrationSpecial Service BehaviourMetrics TIP 13 / 14: Consider Service Templates to make iteasy to do the right thing!Downstream@javazone @samnewman 167. @javazone @samnewman 168. @javazone @samnewman 169. @javazone @samnewman 170. @javazone @samnewman 171. Choice!Opportunity@javazone @samnewman 172. Choice!OpportunityComplexity@javazone @samnewman 173. Choice!OpportunityMonitoring ComplexityDeploymentSafetyIntegration@javazone @samnewman 174. Choice!OpportunityTIP 14 / 14: Find your own balanceMonitoring ComplexityDeploymentSafetyIntegration@javazone @samnewman 175. 62BuildingMicroservicesDESIGNING FINE-GRAINED SYSTEMSSam Newman 176. Designing For !Rapid Release500 West Madison500 West Madison@javazone @samnewman 177. 500 West Madison500 West MadisonFrom Macro To MicroDesigning For !Rapid Release@javazone @samnewman 178. 500 West Madison500 West MadisonFrom Macro To MicroDesigning For !Rapid Releasehttp://lanyrd.com/profile/samnewman/@javazone @samnewman 179. THANKS!Any questions:@samnewmansnewman@thoughtworks.com