1. Docker + Microservices
in Production
Austin PHP
March 10, 2016

2. Who am I?
Patrick Mizer
❏ Lead Engineer at SpareFoot
❏ 13 years developing for consumer web
❏ ZCE, AWS Associate Architect
patrick@sparefoot.com
GitHub: maximizer

3. ● Think Hotels.com for storage*
● Everything in AWS and (recently) in containers
● Continuous Delivery: ~100 deployments per week
● > 300 production containers
● Services handle hundreds of requests/sec
* This kind of storage...

4. What I will talk about today
● Briefly: Monolithic Architectures & Microservices Architectures
● Briefly: Docker Containers, what are they?
● How to use Rancher & Containers to implement a production
microservices architecture
○ Deployment
○ Service Discovery
○ Load balancing
○ Scaling
● Build something!

5. Monolithic Architecture
Database
Facility
Component
Reservation
Component
Unit
Component
Review
Component
A/B Testing
Component
Authentication
Component
Load Balancer

6. Monolithic Architecture
Database
Facility
Component
Reservation
Component
Unit
Component
Review
Component
A/B Testing
Component
Auth
Component
Load Balancer
● Single codebase
● Easy to deploy and debug
● All logic in memory
● Easy to scale out
● Centralized Ops team can
easily manage

7. Monolithic Architecture
Time
Database
Facility
Component
Reservation
Component
Unit
Component
Review
Component
A/B Testing
Component
Auth
Component
Load Balancer
● Team grows
● Codebase grows
○ Tight coupling of
components
○ Language constraints
● No clear ownership
● Long deployment cycles
● Scaling = all or nothing

8. Microservices Architecture
Facility
Service
Reservation
Service
A/B Testing
Service
Load Balancer
Unit
Service
API GatewayAPI Gateway
A/B Testing
Service
Reservation
Service
Facility
Service
Unit
Service
A/B Testing
DB
Unit DB

9. Microservices Architecture
Facility
Service
Service
Load Balancer
Unit
Service
GatewayAPI Gateway
A/B Testing
Service
Reservation
Service
Facility
Service
Unit
Service
A/B DB
Unit DB
Loosely Coupled
+
Bounded Context

10. Microservice Pros
Facility
Service
Service
Load Balancer
Unit
Service
GatewayAPI Gateway
A/B Testing
Service
Reservation
Service
Facility
Service
Unit
Service
A/B DB
Unit DB
● Independent delivery
● Simpler deployments and
rollbacks.
● Right code or framework for the
service
● Fault Isolation

11. Microservice Challenges
Facility
Service
Service
Load Balancer
Unit
Service
GatewayAPI Gateway
A/B Testing
Service
Reservation
Service
Facility
Service
Unit
Service
A/B DB
Unit DB
● Delivery automation
● Service Discovery
● Operational Overhead
● Networking errors
● DevOps

12. Independent Delivery
Build Build Build
Local Integration Staging Production
Deploy

13. Independent Delivery
Build Build Build
Local Integration Staging Production
Deploy
Blocked!

14. Independent Delivery
Build Build Build
Local Integration Staging Production
Deploy
Build
Build Build Build Deploy
Build DeployBuild

15. Independent Delivery
Build Build Build
Local Integration Staging Production
Deploy
Blocked!
Build
Build Build Build Deploy
Build DeployBuild

16. What is Docker?
Build, ship, and run any application,
anywhere…
● Build: Package your application in a container
● Ship: Move that container from one machine to another
● Run: Execute your application

17. The Container Metaphor

18. The Container Metaphor
Things to
ship
Platforms
for shipped
goods

19. The Container Metaphor
Platforms
for shipped
goods

20. The Container Metaphor

21. The Container Metaphor
Standard Interface
Standard Tools

22. The Container Metaphor
Technologies Platforms

23. The Container Metaphor
Platforms

24. The Container Metaphor

25. The Container Metaphor
Standard Interface
Standard Tools

26. Build: Dockerfile
FROM ubuntu:15.10
# Install PHP, and Apache
RUN apt-get update &&
apt-get -yq install
curl
apache2
libapache2-mod-php5
php5
# Copy code
RUN rm -r /var/www/html
COPY index.php /var/www/html/index.php
# Expose port and run apache
EXPOSE 80
CMD ["apachectl", "-D", "FOREGROUND"]

27. Build: Dockerfile
Code
Repository
Host 1
ContainerNew
Docker Engine
Build
Dockerfile
+
Code

28. Ship: Push & Pull
Code
Repository
Host 1
Docker
Image
Registry
ContainerNew
Docker Engine
Build
Push
Dockerfile
+
Code
Container2
Container1
Container3
Host 2
Docker Engine
Pull

29. Run: docker run
Code
Repository
Host 1
Docker
Image
Registry
ContainerNew
Docker Engine
Build
Push
Dockerfile
+
Code
Container2
Container1
Container3
ContainerNew
Host 2
Docker Engine
Pull
Run

30. Run: docker run
Container2
Container1
Container3
ContainerNew
Host 2
Docker Engine
Run
Running a container is fast!
EC2 Instances = minutes
Containers = milliseconds
$ time docker run hello-world
real 0m0.435s
user 0m0.028s

31. Facility
Service
Service
GatewayAPI Gateway
A/B Testing
Service
Reservation
Service
Facility
Service
Microservices
Application Isolation
1 microservice per container, each
containers is independent.
Heterogeneous Tech
Language and framework are specific
to the container.
Easy Deployments
We can push and pull images for free
with Docker.
Orchestration Tools
Swarm, Compose, ECS, Tutum,
Mesos, Kubernetes, and Rancher.

32. Docker + Microservice in Prod
Our (abridged) production checklist:
● Deploy and Schedule
● Build in fault tolerance
● Service Discovery
● Scale

33. Docker Orchestration

34. ● Resource Management
● Container Networking
● Service Discovery
● Load Balancing
Rancher Server
$ docker run -d --restart=always -p 8080:8080 rancher/server

35. Rancher Concepts
● Hosts
● Stacks
Systems
Architecture
(hosts)
Container
Architecture
(stacks)
Deploy
Networking
Discovery
Deploy
Scheduling
Scaling

36. Load
Balancer
Service
container container
containercontainer
container container
link
Rancher: Container Architecture
● Stack
○ Services
○ Containers
● Load Balancer
● Links (cross stack)
LB

37. Deploying containers
Code
Repository
Host 1
Docker
Image
Registry
ContainerNew
Docker Engine
Build
Push
Dockerfile
+
Code
Container2
Container1
Container3
ContainerNew
Host 2
Docker Engine
Pull
Run

38. MASTER
BRANCH A
Dev Staging Production

39. MASTER
BRANCH A
Dev Staging Production

40. MASTER
BRANCH A
Dev Staging
Service1
service1:prod
Production
Service1
service1:stage
Service1
service1:dev-branch-name

41. MASTER
BRANCH A
Service1
service1:prod
rancher-compose

42. MASTER
BRANCH A
Service1
service1:prod
Service1
service1:stage
Service1
service1:dev-branch-name
Service1
Service2
Service3
App1 App2
HTTP

43. Fault Tolerance - AWS + Rancher
ELB
LB LB
US-EAST-1-A US-EAST-1-C
LB
US-EAST-1-B
www

44. Scheduling and Scaling
AWS Autoscaling Group
Container Scale

45. So, let’s build something
Public Load
Balancer
Random Number
Service
Web
Private Load
Balancer
www Requirements
● Public access on port 80 to webheads
● Private access only to our super secure
Random Number Service
● Fault Tolerant
○ Can persist one host failing
● Can scale both web and service
independently

46. Our Service
Public Load
Balancer
Random Number
Service
Web
Private Load
Balancer
www
<?php
$ret = ["server_ip" => $_SERVER['SERVER_ADDR'],
"remote_ip" => $_SERVER['REMOTE_ADDR'],
"x_forwarded_for" =>
$_SERVER['HTTP_X_FORWARDED_FOR'],
"random_number_generator" => rand(0, 100)];
echo json_encode($ret);

47. Our Web head
Public Load
Balancer
Random Number
Service
Web
Private Load
Balancer
www
<?php
$randomNumberResponse =
file_get_contents(getenv("RANDOM_NUMBER_URL"));
$randomArr = json_decode(
$randomNumberResponse, true);
?>
<h1>Hello, your random number is:
<?=$randomArr['random_number_generator']?> </h1>

48. Live demo!

49. Thank you!
My containers:
https://quay.io/repository/patjmizer/php-meetup-web
https://quay.io/repository/patjmizer/php-meetup-service
The code:
https://github.com/maximizer/php-meetup-docker
Wanna talk shop? Reach out:
● Email: patrick@sparefoot.com
Questions?