Or, how NGINX can act as your stevedores properly routing and accelerating HTTP and TCP traffic to pods of containers across a globally distributed environment. NGINX can be used to manage and route your traffic across your distributed micro services architecture offering a seamless interface to your customers and giving you granular management of backend service scaling and versions. Add in some caching and load balancing and the efficiencies of an application delivery platform become apparent.

1. Interconnecting containers at
scale with NGINX

2. @sarahnovotny
#dockercon

3. Building a great application
is only half the battle,
delivering the application
is the other half.

4. MORE INFORMATION AT NGINX.COM
Microservices

5. 1)
The good
things

6. MORE INFORMATION AT NGINX.COM
Microservices + containers

7. The Microservices Architecture:
Enables continuous delivery,
rapid deployment and elasticity

8. MORE INFORMATION AT NGINX.COM
The Microservices Architecture:
To scale, you can scale each
service independently

9. MORE INFORMATION AT NGINX.COM
The Microservices Architecture:
Services can be written in
different languages using
different frameworks

10. MORE INFORMATION AT NGINX.COM
Making Changes:
Each service can be changed,
tested and built independently

11. MORE INFORMATION AT NGINX.COM
Making Changes:
Release cycles can be
dramatically shortened

12. MORE INFORMATION AT NGINX.COM
Deploying Microservices:
To unlock the potential of
microservices you must
embrace containers, cloud and
DevOps

13. 2)
The bad things

14. The Microservices Architecture:
Services can be written in
different languages using
different frameworks

15. Making Changes:
Release cycles can be
dramatically shortened

16. Complexity:
To unlock the potential of
microservices you must
embrace containers, cloud and
DevOps

17. MORE INFORMATION AT NGINX.COM
Here be dragons

18. 3)
How can
NGINX help?

19. Performance
is user experience.

20. Our users are our
community of developers,
devops, sysadmins, cloud
engineers & network
admins

21. NGINX as your stevedores:
Acts as a HTTP router
inspecting requests and
deciding how each one should
be satisfied

22. ste·ve·dore
ˈstēvəˌdôr/
noun
noun: stevedore; plural noun: stevedores
a person employed, or a contractor engaged,
at a dock to load and unload cargo from ships.

23. The Microservices Architecture

24. The Microservices Architecture

25. Docker orchestration
many options vying
(and then there’s service
discovery)

26. 2013 --bloody edge
2014 --roll your own
2015 --lots of options
2016 --convergence?

27. MORE INFORMATION AT NGINX.COM
docker-compose

28. MORE INFORMATION AT NGINX.COM
This .yml file builds –
Consul for service
discovery
Registrator
tutum/hello-world
Google/golang-hello
& NGINX Plus

29. MORE INFORMATION AT NGINX.COM
$ sarah@ubuntu:~/service-discovery$ more docker-compose.yml
nginx:
build: ./nginxplus
links:
- consul
ports:
- "9050:80"
- "8080:8080"
consul:
command: -server -bootstrap -advertise 10.0.2.15
image: progrium/consul:latest
ports:
- "8300:8300"
- "8400:8400"
- "8500:8500"
- "8600:53/udp”

30. MORE INFORMATION AT NGINX.COM
registrator:
command: consul://consul:8500
image: progrium/registrator:latest
links:
- consul
volumes:
- "/var/run/docker.sock:/tmp/docker.sock"
service1:
image: tutum/hello-world:latest
environment:
SERVICE_80_NAME: http
SERVICE_NAME: service1
SERVICE_TAGS: production
ports:
- "80"

31. MORE INFORMATION AT NGINX.COM
service2:
image: google/golang-hello:latest
environment:
SERVICE_80_NAME: http
SERVICE_NAME: service2
SERVICE_TAGS: production
ports:
- "8080"
sarah@ubuntu:~/service-discovery$

32. MORE INFORMATION AT NGINX.COM
sarah@ubuntu:~/service-discovery$ docker-compose build
consul uses an image, skipping
Building nginx...
Step 0 : FROM ubuntu:14.04
---> 6d4946999d4f
Step 1 : MAINTAINER NGINX Docker Maintainers "docker-maint@nginx.com"
---> Using cache
---> 339d0f20dc6e
…
sarah@ubuntu:~/service-discovery$ docker-compose up -d
Recreating servicediscovery_consul_1...
Recreating servicediscovery_nginx_1...
Recreating servicediscovery_registrator_1...
Recreating servicediscovery_service1_6...
Recreating servicediscovery_service2_1...
sarah@ubuntu:~/service-discovery$

33. MORE INFORMATION AT NGINX.COM

34. MORE INFORMATION AT NGINX.COM

35. MORE INFORMATION AT NGINX.COM
sarah@ubuntu:~/service-discovery/nginxplus$ more nginx.conf
{{range services}} {{$name := .Name}} {{range $tag, $service := service .Name |
byTag}} {{if eq $tag "production"}}
upstream {{$name}} {
zone upstream-{{$name}} 64k;
least_conn;
{{range $service}}server {{.Address}}:{{.Port}} max_fails=3 fail_timeout=60
weight=1 slow_start=60;
{{else}}server 127.0.0.1:65535; # force a 502{{end}}
} {{end}} {{end}} {{end}}
<snip>

36. MORE INFORMATION AT NGINX.COM
sarah@ubuntu:~/service-discovery$ docker-compose scale service1=5
Creating servicediscovery_service1_2...
Creating servicediscovery_service1_3...
Creating servicediscovery_service1_4...
Creating servicediscovery_service1_5...
Starting servicediscovery_service1_2...
Starting servicediscovery_service1_3...
Starting servicediscovery_service1_4...
Starting servicediscovery_service1_5...

37. MORE INFORMATION AT NGINX.COM

38. MORE INFORMATION AT NGINX.COM

39. The Microservices Architecture

40. MORE INFORMATION AT NGINX.COM
Visit our kiosk
tomorrow to go
through this
demo
It was based on a blog post for
bellycard by @shanesveller
And built by @fymemon

41. Thank you
@sarahnovotny
#dockercon