Webinar recording: nginx.com/resources/webinars/microservices-container-management-nginx-plus-mesosphere-dcos NGINX and NGINX Plus are emerging as the standard for connecting, securing, caching, and scaling microservices. We hope you found it valuable to learn how to use Mesosphere DC/OS and containers, such as Docker containers, to create and run microservices applications in an NGINX Plus environment.

1. Microservices and
Container Management
with NGINX Plus and
Mesosphere DC/OS
April 20, 2016

2. MORE INFORMATION AT
NGINX.COM
Christopher
Stetson
Chief Architect,
Professional Services
NGINX
Ben
Horowitz
Technical Architect,
Professional Services
NGINX

3. MORE INFORMATION AT
NGINX.COM
Agenda
• NGINX Microservices Reference Architecture
• Mesosphere DC/OS
• Docker Image CI/CD
• Developer UI
• Robust Networking Options
• Warts & All
• Conclusion

4. MORE INFORMATION AT
NGINX.COM
NGINX Microservices
Reference
Architecture

5. MORE INFORMATION AT
NGINX.COM
NGINX = Microservices

6. MORE INFORMATION AT
NGINX.COM
Microservices
Architecture
• Docker containers
• Polyglot services
• 12-Factor App(-esque)
design

7. MORE INFORMATION AT
NGINX.COM

8. MORE INFORMATION AT
NGINX.COM

9. MORE INFORMATION AT
NGINX.COM
Value of MSA
• Provide customers with a
microservices blueprint
• Test out NGINX and
NGINX Plus features for
microservices
• Understand the
microservices ecosystem

10. MORE INFORMATION AT
NGINX.COM

11. MORE INFORMATION AT
NGINX.COM
Mesosphere DC/OS

12. MORE INFORMATION AT
NGINX.COM
Docker Image
CI/CD

13. MORE INFORMATION AT
NGINX.COM
Typical CI/CD
• Developers submit code
to the Version Control
System (VCS)
• Continuous integration
(CI) server grabs code,
builds, tests, and deploys
• Critical process for
microservices

14. MORE INFORMATION AT
NGINX.COM
Bake vs. Fry
• Bake: create a durable
artifact that is deployed
throughout system
• Fry: build artifact as
needed for each
environment
• Docker images could be
ultimate baked good

15. MORE INFORMATION AT
NGINX.COM
Docker Image
CI/CD
• Commit to VCS
• CI/CD creates image and
deploys to repo
• Tests are conducted
against image

16. MORE INFORMATION AT
NGINX.COM
DC/OS Repo
Support
• Most systems only
support public repo
(DockerHub)
• Include repo credentials
in app definition JSON file
• forcePullImage to avoid
local image caching
"container": {
"type": "DOCKER",
"docker": {
"image": "docker.io/<docker-image>",
"forcePullImage": true,
"network": "BRIDGE",
"portMappings": [
{
"containerPort": 443,
"hostPort": 0,
"protocol": "tcp"
}
]
}
},
"uris": [
"https://s3.amazonaws.com/docker_credentials.gz"
]
}

17. MORE INFORMATION AT
NGINX.COM
Robust UI/UX

18. MORE INFORMATION AT
NGINX.COM
Developer’s Swiss Army
Knife
• Nice web UI
• Solid CLI
• Robust API

19. MORE INFORMATION AT
NGINX.COM
Beauty Is More
than Skin-Deep
• Overview of system
• Monitoring of apps
• Configuration and
management

20. MORE INFORMATION AT
NGINX.COM
Not Just A
Pretty Face
• The CLI is a critical piece
of software
• How you manage and
deploy your apps
• Monitoring features

21. MORE INFORMATION AT
NGINX.COM
API to Do Even
More
• API provides all data and
capabilities of Marathon
• Mesos also has an API
for more fundamental
actions
• Fully scriptable system

22. MORE INFORMATION AT
NGINX.COM
Robust Networking
Options

23. MORE INFORMATION AT
NGINX.COM
DC/OS Unopinionated

24. MORE INFORMATION AT
NGINX.COM
Proxy Model
• Simple networking model
• Good for flat APIs or
simple apps
• Round-robin DNS
interservice connection

25. MORE INFORMATION AT
NGINX.COM
Router Mesh
Model
• NGINX Plus as the proxy
• NGINX Plus running on
hosts and providing
intraservice connectivity
• Intelligent load balancing
with active health checks

26. MORE INFORMATION AT
NGINX.COM
Fabric Model
• NGINX Plus running in
each container
• DNS service discovery
• Persistent SSL/TLS
connections
• Health checks provide
circuit-breaker pattern

27. MORE INFORMATION AT
NGINX.COM
Warts & All

28. MORE INFORMATION AT
NGINX.COM
Not All Cookies
and Cream
• Cached Docker images
• Confusing nomenclature
• Useful features not
implemented in UI − for
example, logging

29. MORE INFORMATION AT
NGINX.COM
Conclusion