Deploying and Scaling Microservices
•
32 likes•4,738 views
The challenges of managing many, smaller deployable services mean that what we need in terms of deployment platforms are very different to what was needed before. But few areas of software technology have been experiencing as much innovation and churn as the deployment options available for microservice architectures. From appication containers, to docker, to mesos and beyond, this talk will break apart the myriad challenges that can come from managing microservices at scale, and how to pick the right technologies for you.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (19)
Similar to Deploying and Scaling Microservices
Similar to Deploying and Scaling Microservices (20)
Recently uploaded
Recently uploaded (20)
Deploying and Scaling Microservices
- 2. @samnewman
- 21. @samnewman TestsBuild Performance ProdUAT https://www.flickr.com/ Source Control ! ! ! One Artifact For All Environments
- 22. @samnewman TestsBuild Performance ProdUAT https://www.flickr.com/ Source Control ! ! ! One Artifact For All Environments Same Deployment Process Everywhere
- 23. @samnewman $ deploy Returns v456 Production
- 24. @samnewman $ deploy Returns v456 Production Service Name
- 25. @samnewman $ deploy Returns v456 Production Service Name Version
- 26. @samnewman $ deploy Returns v456 Production local Service Name Version
- 27. @samnewman $ deploy Returns v456 Production local latest Service Name Version
- 28. @samnewman $ deploy Returns v456 Production local latest Service Name Version Environment
- 29. @samnewman TestsBuild Large TestsUAT Prod DB Machine UAT Environment Machine Perf
- 30. @samnewman TestsBuild UAT Perf Master DB Machine Perf Environment Machine Machine Machine Slave DB Perf Prod
- 31. @samnewman TestsBuild UAT Perf Prod Master DB Machine Production Environment Machine Machine Machine Slave DB
- 36. @samnewman Independent Deployability One Artifact For All Environments Core Principles?
- 37. @samnewman Independent Deployability One Artifact For All Environments Same Deployment Process Everywhere Core Principles?
- 39. @samnewman What do we want from an artifact?
- 40. @samnewman What do we want from an artifact?
- 41. @samnewman What do we want from an artifact? Easy to create
- 42. @samnewman What do we want from an artifact? Easy to deploy Easy to create
- 43. @samnewman What do we want from an artifact? Easy to deploy Abstract out the tech stack Easy to create
- 44. @samnewman What do we want from an artifact? Easy to deploy Abstract out the tech stack Good for dev, good for ops Easy to create
- 46. @samnewman Tarballs Giant bundles of stuff
- 47. @samnewman Tarballs Easy to create Easy to deploy Abstract out the tech stack Good for dev, good for ops
- 48. @samnewman Tarballs Easy to create! Easy to deploy Abstract out the tech stack Good for dev, good for ops
- 49. @samnewman Tarballs Easy to create! Easy to deploy" Abstract out the tech stack Good for dev, good for ops
- 50. @samnewman Tarballs Easy to create! Easy to deploy" Abstract out the tech stack# Good for dev, good for ops
- 51. @samnewman Tarballs Easy to create! Easy to deploy" Abstract out the tech stack# Good for dev, good for ops"
- 54. @samnewman Stack-specific Easy to create Abstract out the tech stack Easy to deploy Good for dev, good for ops
- 55. @samnewman Stack-specific Easy to create! Abstract out the tech stack Easy to deploy Good for dev, good for ops
- 56. @samnewman Stack-specific Easy to create! Abstract out the tech stack Easy to deploy# Good for dev, good for ops
- 57. @samnewman Stack-specific Easy to create! Abstract out the tech stack" Easy to deploy# Good for dev, good for ops
- 58. @samnewman Stack-specific Easy to create! Abstract out the tech stack" Easy to deploy# Good for dev, good for ops"
- 59. @samnewman Everything in Go is Awesome
- 60. @samnewman Everything in Go is Awesome FACT
- 62. @samnewman OS-Specific $ sudo apt-get install myservice
- 63. @samnewman OS-Specific $ sudo apt-get install myservice $ deploy Returns v456 Production
- 64. @samnewman OS-Specific Easy to deploy Easy to create Abstract out the tech stack Good for dev, good for ops
- 65. @samnewman OS-Specific Easy to deploy Easy to create" Abstract out the tech stack Good for dev, good for ops
- 66. @samnewman OS-Specific Easy to deploy! Easy to create" Abstract out the tech stack Good for dev, good for ops
- 67. @samnewman OS-Specific Easy to deploy! Easy to create" Abstract out the tech stack! Good for dev, good for ops
- 68. @samnewman OS-Specific Easy to deploy! Easy to create" Abstract out the tech stack! Good for dev, good for ops#
- 69. @samnewman Build
- 74. @samnewman
- 78. @samnewman Host
- 79. @samnewman Host
- 81. @samnewman Host Host Host Host Independent Execution Environments FTW!
- 82. @samnewman Custom Images Easy to deploy Easy to create Abstract out the tech stack Good for dev, good for ops
- 83. @samnewman Custom Images Easy to deploy Easy to create# Abstract out the tech stack Good for dev, good for ops
- 84. @samnewman Custom Images Easy to deploy# Easy to create# Abstract out the tech stack Good for dev, good for ops
- 85. @samnewman Custom Images Easy to deploy# Easy to create# Abstract out the tech stack Good for dev, good for ops !
- 86. @samnewman Custom Images Easy to deploy# Easy to create# Abstract out the tech stack Good for dev, good for ops ! #
- 87. @samnewman
- 88. @samnewman
- 89. @samnewman Cost of isolated hosts is reduced…
- 90. @samnewman Cost of isolated hosts is reduced… …in terms of effort…
- 91. @samnewman Cost of isolated hosts is reduced… …in terms of effort… …and computing resources
- 92. @samnewman Docker! Easy to deploy Abstract out the tech stack Good for dev, good for ops Easy to create
- 93. @samnewman Docker! Easy to deploy Abstract out the tech stack Good for dev, good for ops Easy to create#
- 94. @samnewman Docker! Easy to deploy Abstract out the tech stack Good for dev, good for ops Easy to create ! #
- 95. @samnewman Docker! Easy to deploy Abstract out the tech stack Good for dev, good for ops Easy to create ! ! #
- 96. @samnewman Docker! Easy to deploy Abstract out the tech stack Good for dev, good for ops Easy to create ! ! # #
- 98. @samnewman What do we want from our deployment platform?
- 99. @samnewman What do we want from our deployment platform? Separate artifact from topology
- 100. @samnewman What do we want from our deployment platform? Separate artifact from topology Makes handling lots of services easy!
- 101. @samnewman What do we want from our deployment platform? Separate artifact from topology Makes handling lots of services easy! Supports docker images
- 109. @samnewman DOCKER SWARM Swarm Node Swarm Node Swarm Node Swarm Manager
- 110. @samnewman DOCKER SWARM Swarm Node Swarm Node Swarm Node Swarm Manager
- 111. @samnewman DOCKER SWARM Swarm Node Swarm Node Swarm Node Swarm Manager $ docker …
- 112. @samnewman DOCKER SWARM Swarm Node Swarm Node Swarm Node Swarm Manager $ docker …
- 113. @samnewman DOCKER SWARM Swarm Node Swarm Node Swarm Node Swarm Manager $ docker …
- 114. @samnewman DOCKER SWARM Swarm Node Swarm Node Swarm Node Swarm Manager $ docker …
- 115. @samnewman SCHEDULING STRATEGIES - BINPACK Swarm Node Swarm Node Swarm Node Swarm Manager
- 116. @samnewman SCHEDULING STRATEGIES - BINPACK Swarm Node Swarm Node Swarm Node Swarm Manager
- 117. @samnewman SCHEDULING STRATEGIES - SPREAD Swarm Node Swarm Node Swarm Node Swarm Manager
- 118. @samnewman SCHEDULING STRATEGIES - SPREAD Swarm Node Swarm Node Swarm Node Swarm Manager
- 119. @samnewman DOCKER COMPOSE web: build: . ports: - "5000:5000" volumes: - .:/code links: - redis redis: image: redis
- 120. @samnewman
- 122. @samnewman Doesn’t rebalance Doesn’t restart failed containers
- 123. @samnewman Doesn’t rebalance Doesn’t restart failed containers Plays nice with the rest of docker
- 124. @samnewman Doesn’t rebalance Doesn’t restart failed containers Plays nice with the rest of docker Case studies thin on the ground
- 125. @samnewman
- 128. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS
- 130. @samnewman
- 134. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS
- 135. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Scheduler
- 136. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Executor Hadoop Scheduler
- 137. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Executor Hadoop Scheduler
- 138. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Executor Hadoop Scheduler Hadoop
- 139. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Executor Hadoop Scheduler Hadoop Marathon Marathon
- 140. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Executor Hadoop Scheduler Hadoop Marathon Marathon Marathon Scheduler
- 141. @samnewman Mesos Master Mesos Agent Mesos Agent Mesos Agent MESOS Hadoop Executor Hadoop Scheduler Hadoop Marathon Marathon Marathon Scheduler
- 144. @samnewman
- 145. @samnewman Great if you need to run other workloads
- 146. @samnewman Great if you need to run other workloads Really powerful - fully featured, widely used
- 147. @samnewman Great if you need to run other workloads Really powerful - fully featured, widely used Fairly complex - lots of moving parts
- 148. @samnewman
- 149. @samnewman
- 153. @samnewman API Server Kubelet Kubelet Kubelet KUBERNETES ARCHITECTURE…SORT OF
- 154. @samnewman API Server Kubelet Kubelet Kubelet $ kubectl … KUBERNETES ARCHITECTURE…SORT OF
- 155. @samnewman API Server Kubelet Kubelet Kubelet $ kubectl … KUBERNETES ARCHITECTURE…SORT OF
- 156. @samnewman PODS?
- 157. @samnewman A collection of tightly coupled containers, running on one node PODS?
- 158. @samnewman A collection of tightly coupled containers, running on one node PODS? Can have metadata, volumes too
- 159. @samnewman A collection of tightly coupled containers, running on one node PODS? Can have metadata, volumes too Pods are mortal - not long running!
- 160. @samnewman A collection of tightly coupled containers, running on one node PODS? Can have metadata, volumes too Pods are mortal - not long running! A pod = a unit of scheduling
- 161. @samnewman SERVICES!
- 162. @samnewman SERVICES! { "kind": "Service", "apiVersion": "v1", "metadata": { "name": "my-service" }, "spec": { "selector": { "app": "MyApp" }, "ports": [ { "protocol": "TCP", "port": 80, "targetPort": 9376 } ] } }
- 163. @samnewman SERVICES! A mapping of metadata and ports to a set of pods { "kind": "Service", "apiVersion": "v1", "metadata": { "name": "my-service" }, "spec": { "selector": { "app": "MyApp" }, "ports": [ { "protocol": "TCP", "port": 80, "targetPort": 9376 } ] } }
- 164. @samnewman JSON is neither human readable nor human writeable
- 165. @samnewman JSON is neither human readable nor human writeable Please stop using it for anything other than machines
- 166. @samnewman Kubelet
- 167. @samnewman Kubelet
- 168. @samnewman Kubelet
- 171. @samnewman You don’t scale a service… Kubelet Service Proxy :80
- 172. @samnewman You don’t scale a service… …you scale the pods! Kubelet Service Proxy :80
- 173. @samnewman
- 174. @samnewman Simpler to setup than Mesos - but more single purpose too
- 175. @samnewman Simpler to setup than Mesos - but more single purpose too Closer to a PAAS
- 176. @samnewman Simpler to setup than Mesos - but more single purpose too Closer to a PAAS Pods can be confusing!
- 177. @samnewman Simpler to setup than Mesos - but more single purpose too Closer to a PAAS Fairly new, but a growing amount of impressive support Pods can be confusing!
- 182. @samnewman
- 185. @samnewman Core Principles One Artifact For All Environments Independent Deployability
- 186. @samnewman Core Principles One Artifact For All Environments Independent Deployability Same Deployment Process
- 187. @samnewman Core Principles One Artifact For All Environments Independent Deployability Same Deployment Process Docker Images As Artifacts
- 188. @samnewman Core Principles One Artifact For All Environments Independent Deployability Same Deployment Process Docker Images As Artifacts Criteria For Selecting A Platform
- 189. @samnewman
- 190. @samnewman Sam Newman Building Microservices DESIGNING FINE-GRAINED SYSTEMS AUTHD
- 191. @samnewman Sam Newman Building Microservices DESIGNING FINE-GRAINED SYSTEMS AUTHD Send me your questions on twitter!
- 192. @samnewman Sam Newman Building Microservices DESIGNING FINE-GRAINED SYSTEMS AUTHD Send me your questions on twitter! @samnewman
- 193. @samnewman Sam Newman Building Microservices DESIGNING FINE-GRAINED SYSTEMS AUTHD Send me your questions on twitter! @samnewman And I’ll write up an answer for you!