Bastian Hofmann, Software Engineer at SysEleven, выступил на конференции CODEiD – PHP Odessa Conf #4 с темой «Running microservices successfully» «Using microservices can give you a lot of benefits in your application architecture in terms of developer productivity or scalability, but deploying and running them can be quite hard, for example in terms of monitoring or network latencies. In this talk I will show you what you have to keep in mind if you want to keep your microservices running fast and smoothly and how you can solve the problems that will arise when the amount of services or traffic is growing.» CODEiD – это всеукраинское сообщество PHP-разработчиков. Наша цель — создать сильное сообщество всех, кто увлечен PHP-разработкой, и принимать в нашем уютном приморском городе коллег со всей Украины и мира.

1. @BastianHofmann
Running Microservices
Successfully
Bastian Hofmann

2. Microservices

3. Monolith

4. http://blog.philipphauer.de/microservices-nutshell-pros-cons/
Monolith Microservices

5. " Microservices are great for
turning method calls in to
distributed computing
problems
https://twitter.com/tenderlove/status/1027591532847816704

6. Challenges

7. Performance

8. Latency

9. Operational overhead

10. Monitoring

11. Learning Curves

12. Code Reuse

13. Maintenance

14. Benefits

15. Enforces stricter separation of
concerns

16. Diverse technology stacks

17. Independent scaling

18. Independent development

19. Independent deployments

20. There are good reasons to split off
functionality into independent
services

21. How to run Microservices without
shooting yourself in the foot

22. Let's talk about
• Deploying
• Running
• Configuring
• Discovering
• Monitoring
• Scaling

23. A lot of this is also useful for
monoliths

24. https://www.flickr.com/photos/npobre/2601582256/

25. Let's define our requirements

26. Deployment

27. How to get the services on our
servers?

28. Diverse technology stacks

29. The same approach for every service

30. Fast deployments

31. Automation

32. One Click Deployment

33. Fast rollbacks

34. Availability

35. Zero Downtime Deployments

36. Running the service

37. How do I stop and start a service and
ensure it keeps running?

38. Diverse technology stacks

39. Diverse system dependencies

40. The same approach for every service

41. Configuration Management

42. How do I synchronize configuration
over services?

43. Config file on disk

44. [
"db_user": "user",
"db_pw": "pw",
"serviceA": "serviceA.local:8018"
]

45. Duplication

46. Inconsistencies

47. Security

48. Cycling of credentials

49. Service Discovery

50. How does one service know where
another service is?

51. Load balancing?

52. Service/Server down?

53. Health checks

54. Monitoring

55. How do I know how my application is
behaving?

56. Distributed Systems

57. We want to measure

58. Latency

59. Availability

60. Throughput

61. We want all logs aggregated and
searchable

62. Scaling

63. How can I cope with growing traffic?

64. Reacting to changes in traffic?

65. You have to take care about a lot of
things when doing Microservices!

66. There are tools that can help us with
this

68. Container orchestration platform

69. Deploy, run and scale your services
in isolated containers

70. Very Powerful

71. Large community

72. Lot’s of large company backers

73. Compared to other cloud
technoligies

74. No vendor lock in

75. Runs on

76. AWS

77. Azure

78. Google Cloud Platform

79. Bare metal

80. Your laptop

81. SysEleven

82. Learning curve

83. Why containers?

84. Services run in isolation

85. Everything needed to run a service in
one image

86. Decouple
Ops and Dev

87. Make things …

88. Easier to deploy

89. Easier to upgrade system
dependencies

90. Easier to scale

91. Easier to develop

92. Leaner than
Virtual Machines

94. FROM php:7.2-apache
WORKDIR /var/www/html
RUN apt-get update -y &&
apt-get install -y --no-install-recommends curl
rm -rf /var/lib/apt/lists/*
ENV TMP_DIR /tmp
COPY . /var/www/html/
EXPOSE 80
ENTRYPOINT [“apache2”, “-DFOREGROUND”]

95. docker build -t symfony-demo:2.0.0 .

96. docker run -p 8080:80 symfony-demo:2.0.0

97. Kubernetes helps you running
containers

98. Let’s define some core Kubernetes
concepts

99. Kubernetes Cluster

100. • A physical server
• Containers get distributed
automatically
Node

101. • A docker image built from
a Dockerfile that contains
everything a service needs
to run
Image

102. • A container runs a docker
image.
• Only 1 process can run
inside of a container
Container

103. • A group of 1 or more
containers
• Same port space
• Ports are not accessible
from outside of the pod
Pod

104. • Defines and manages how
many instances of a pod
should run
Replica Set

105. • Manages updates and
rollbacks of replica sets
Deployment

106. • Makes a port of a pod
accessible to other pods
Service

107. • Makes a service
accessible to the outside
of Kubernetes
Ingress

108. • Configuration that can be
mounted inside of a
container
ConfigMap

109. • Volumes can be mounted
into a container to access
a ConfigMap, Secret or a
folder on the host
Volumes

110. Example

111. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD

112. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD
ReplicaSet: 2 instances
PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD

113. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
ReplicaSet: 2 instances
PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
CONFIG
WEB :80
PHP Application POD PHP Application POD

114. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
ReplicaSet: 2 instances
PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
CONFIG
WEB :80
https://php-app.k8s.foo.com:443/
PHP Application POD PHP Application POD

115. Let’s deploy the symfony demo app

116. https://github.com/symfony/demo

117. First we need a Kubernetes cluster

122. kubectl

123. $ kubectl get pods

124. NAME READY
STATUS RESTARTS AGE
kubernetes-dashboard-5b5bf59977-t9xb9 1/1
Running 2 9d
nginx-ingress-controller-5549f5597c-97kcw 0/1
Running 2 9d
nginx-ingress-default-backend-564d9d9477-tmnnr 1/1
Running 4 9d
mysql-556c9b5bcb-5jdrt 1/1
Running 1 8d
symfony-demo-5b75f5fc6-c7wr9 1/1
Running 0 8d
symfony-demo-5b75f5fc6-jg8n4 1/1
Running 23 8d

125. Demo

126. Creating a Docker image

127. PHP

128. Copy our code

129. Build the project

130. Composer install

131. yarn install

132. yarn run build

133. Building the image

134. docker build -t symfony-demo:2.0.0 .

135. Now we have to tell Kubernetes
what to do with the image

136. Resources are defined in YAML or
JSON

137. Deployment

138. kind: Deployment
apiVersion: extensions/v1beta1
metadata:
name: symfony-demo
spec:
template:
metadata:
labels:
app: symfony-demo
spec:
containers:
- name: symfony-demo
image: symfony-demo:1.0.0
ports:

139. containers:
- name: symfony-demo
image: symfony-demo:1.0.0
ports:
- containerPort: 80
livenessProbe:
httpGet:
path: /
port: 80
timeoutSeconds: 1
initialDelaySeconds: 10
readinessProbe:
httpGet:
path: /

140. Many more options configurable

141. Many more options
• Setting environment variables
• Mounting volumes
• Requesting resources
• Defining upgrade strategies
• Defining command
• Configure networking
• Configure the scheduler
• Listen on lifecycle events
• Configure system capabilities for the container
• …

142. Service

143. kind: Service
apiVersion: v1
metadata:
name: symfony-demo
spec:
ports:
-
name: http
port: 80
targetPort: 80
protocol: TCP
selector:
app: symfony-demo

144. Ingress

145. kind: Ingress
apiVersion: extensions/v1beta1
metadata:
name: symfony-demo
spec:
rules:
- host: symfony-demo.local.k8s
http:
paths:
- path: /
backend:
serviceName: symfony-demo
servicePort: 80

146. Creating everything

147. kubectl apply -f deployment/webapp.yaml

149. Rolling Deployments

150. kind: Deployment
apiVersion: extensions/v1beta1
metadata:
name: symfony-demo
spec:
template:
spec:
containers:
- name: symfony-demo
image: symfony-demo:1.1.0
ports:
- containerPort: 80

151. kubectl apply -f deployment/webapp.yaml

152. Rollback

153. $ kubectl rollout undo deployments symfony-deom --to-
revision=1

154. Configuration

155. Should not be included in the docker
image

156. ConfigMap

157. Key/Value Store

158. kind: ConfigMap
apiVersion: v1
metadata:
name: special-config
data:
special-key: value
bool-value: true

159. Can be accessed in a pod through
environment variables

160. spec:
containers:
- name: test-container
image: k8s.gcr.io/busybox
command: [ "/bin/sh", "-c", "env" ]
env:
- name: SPECIAL_KEY
valueFrom:
configMapKeyRef:
name: special-config
key: special-key

161. spec:
containers:
- name: test-container
image: k8s.gcr.io/busybox
command: [ "/bin/sh", "-c", "env" ]
envFrom:
- configMapRef:
name: special-config

162. Can be accessed through volumes

163. spec:
containers:
- name: test-container
image: k8s.gcr.io/busybox
command: [ "/bin/sh", "-c", "ls /etc/config/" ]
volumeMounts:
- name: config-volume
mountPath: /etc/config
volumes:
- name: config-volume
configMap:
name: special-config

164. Service Discovery

165. Within a pod

166. Shared port namespace

167. Separate file systems

168. Separate process spaces

169. Network wise everything behaves
like localhost

170. Between pods

171. You have to expose ports with
services

172. kind: Service
apiVersion: v1
metadata:
name: symfony-demo
spec:
ports:
-
name: http
port: 80
targetPort: 80
protocol: TCP
selector:
app: symfony-demo

173. Every service has a virtual IP address

174. $ kubectl get service symfony-demo
NAME TYPE CLUSTER-IP PORT(S) AGE
symfony-demo ClusterIP 10.106.119.24 80/TCP 6d

175. Discoverable in other containers by

176. Environment Variables

177. SYMFONY_DEMO_SERVICE_HOST=10.106.119.24
SYMFONY_DEMO_SERVICE_PORT=80

178. DNS

179. $ nslookup symfony-demo
Server: 10.0.0.10
Address 1: 10.0.0.10
Name: symfony-demo
Address 1: 10.106.119.24

180. $ curl http://symfony-demo

181. Service Mesh

182. Istio
https://istio.io/

183. LinkerD
https://linkerd.io/

184. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD

185. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD
NodeJS ISTIO
NodeJS Service POD
NodeJS ISTIO
NodeJS Service POD

186. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD
NodeJS ISTIO
NodeJS Service POD
NodeJS ISTIO
NodeJS Service POD

187. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD
NodeJS ISTIO
NodeJS Service POD
NodeJS ISTIO
NodeJS Service POD

188. PHP-FPM
NGINX
ISTIO
STATSD
MEM
CACHED
MONGO
ROUTER
PHP Application POD
NodeJS ISTIO
NodeJS Service POD
NodeJS ISTIO
NodeJS Service POD

189. Benefits

190. Advanced routing

191. Prefer service in current namespace,
fall back to default namespace

192. A/B Testing
https://medium.com/vamp-io/a-b-testing-on-kubernetes-with-istio-0-8-6323efa2b4e2

193. Canary deployments
https://istio.io/blog/2017/0.1-canary/

194. Circuit Breakers
https://istio.io/docs/tasks/traffic-management/circuit-breaking/

195. Security
https://istio.io/blog/2017/0.1-auth/

196. Advanced monitoring

198. Profiling

200. Monitoring

201. Metrics-Server

202. Takes metrics from Kubernetes and
stores them in a monitoring solution

203. e.g. Prometheus

204. Combine with metrics of other
components

205. Service Mesh

206. Your services

207. Grafana for displaying the data

210. Logging

211. kubectl logs

212. $ kubectl logs symfony-demo-5b75f5fc6-c7wr9

213. One interface

214. Easy to pipe into central log
management system

215. Scaling

216. Manual Scaling

217. kubectl scale --replicas=3 deployment/my-app

218. AutoScaling

219. https://kubernetes.io/docs/user-guide/
horizontal-pod-autoscaling/

220. Summary

221. Powerful

222. Helpful

223. Together with the whole Eco-System

224. And Docker

225. Kubernetes helps you to run
microservices successfully

226. By standardizing Deployment,
Scaling, Configuration, Monitoring,
Service Discovery, Health Checks, ...

227. http://speakerdeck.com/
u/bastianhofmann

228. Vielen Dank für Ihre Aufmerksamkeit!