Using Docker and Elastic Beanstalk in Production
0 likes280 views
This document discusses using Docker and Elastic Beanstalk for deploying microservices architectures in production. It covers moving from monolithic to service-oriented architectures, and advantages of treating infrastructure as "cattle" rather than "pets". Docker is introduced as a way to package applications into lightweight, portable containers instead of virtual machines. Configuration steps are outlined for building Docker images, pushing them to Docker Hub, and deploying containers to Elastic Beanstalk. Health checks, Node.js configuration, and application monitoring strategies are also briefly discussed.
![Node.js Specific Notes For Production
Supervisor Conf
[supervisord]
nodaemon=true
[program:grunt]
command=grunt
autorestart=true
Dockerfile
#Install Supervisor
RUN apt-get install -y supervisor
RUN mkdir -p /var/log/supervisor
COPY supervisord.conf /etc/supervisor/conf.d/supervisord.conf
#Switch to the container local version of the application
WORKDIR /usr/src/app
#TEll docker what port to look at for your app
EXPOSE 5000
#Start the Application
CMD ["/usr/bin/supervisord"]](https://image.slidesharecdn.com/april72016awsmeetuppresentation-160408181834/85/Using-Docker-and-Elastic-Beanstalk-in-Production-45-320.jpg)
Using Docker and Elastic Beanstalk in Production
- 1. Using Docker and Elastic Beanstalk in Production Taking the leap from the Monolithic application to service oriented architecture.
- 7. PIVOT TIME! 2006 Social Network for reviewing businesses!
- 11. We Sucked!
- 20. Business is good. But we’ve got Tech Debt!
- 25. SOA Monolithic Architecture Service Oriented Architecture
- 28. From Pets to Cattle to Bacteria to to
- 29. Pets vs Cattle VS Pets: - Server typically on site, own and maintain - Server tied to App - Named (universe, saturn, pluto) Cattle: - Improved Resource utilization - Typically off site - Vendor Maintained - Problems? Just delete. - Done? Delete
- 30. Pets vs Cattle VS Cattle: - VMs are “Heavyweight” - Images are hard to upload - Not Portable - Typically “Long Lived” Bacteria: - Lightweight (can be just one process) - A process isolator - Alive for minutes
- 31. So why use Docker? reproducibility
- 32. What Is Docker?
- 36. Docker containers Docker containers are similar to a directory. A Docker container holds everything that is needed for an application to run. Each container is created from a Docker image. Docker containers can be run, started, stopped, moved, and deleted. Each container is an isolated and secure application platform. Docker containers are the runcomponent of Docker. Docker images A Docker image is a read-only template. For example, an image could contain an Ubuntu operating system with Apache and your web application installed. Images are used to create Docker containers. Docker provides a simple way to build new images or update existing images, or you can download Docker images that other people have already created. Docker images are the build component of Docker. BUILD RUN
- 37. Docker Files
- 39. Build Vs Run
- 40. Docker Hub
- 41. Docker Hub to Elastic Beanstalk credentials on S3
- 42. Configuring and launching to Elastic Beanstalk.
- 43. Health Checks should check your application, not Nginx
- 44. Remember Nginx is in front of your container on EB
- 45. Node.js Specific Notes For Production Supervisor Conf [supervisord] nodaemon=true [program:grunt] command=grunt autorestart=true Dockerfile #Install Supervisor RUN apt-get install -y supervisor RUN mkdir -p /var/log/supervisor COPY supervisord.conf /etc/supervisor/conf.d/supervisord.conf #Switch to the container local version of the application WORKDIR /usr/src/app #TEll docker what port to look at for your app EXPOSE 5000 #Start the Application CMD ["/usr/bin/supervisord"]
- 46. Application monitoring, Needs to be external