Sr. Software Engineer @lucidspring/remote

• Why you should learn it
  • Environment uniformity
  • Market demand
  • Microservices
  • Personal usage
• Docker Architecture (overview)
• Getting straight into Docker
  • Dockerfile ?
  • Basic Docker commands
  • Understanding container, Image and Dockerfile
  • Types of docker images (overview of Docker Hub)
• Dockerizing Node.js codebases (live)
  • ​Volume and types
• Hooking up with Dockerized database
• Docker-Compose in action
  • Migrate all individual services to Docker-Compose
  • Understanding network layer
  • Understanding docker-compose flags 
• Adding NGINX as a reverse proxy (container to containers)

• Uniformity of environment
• Market Demand
• Most important tool for Microservices
• Automation
• Great of managing multiple system-level softwares

• Every VM has an Operating System
• Every OS requires its own bandwidth, memory, and compute
• High load time
• Individual patches, updates and security checks
• Mindset of Monolith

• Uses HTTP as communication layer
• Client could be CLI, Docker-Dashboard, VSCode Extension, etc
• Docker Daemon does the layer resource checking, caching, downloading

• Container
  • The image when it is ‘running.’ The standard unit for app service
• Image
  • A readonly pack of environment and sets of instructions to create/run a container
• Dockerfile
  • ​A snapshot of set of instructions
• Engine
  • ​The software that executes commands for containers. Networking and volumes are part of Engine. 
• Registry ​

  • Stores, distributes and manages Docker images,

  • Github for Containers

• Control Plane

  • ​Management plane for container and cluster orchestration

• Bridge Network
• Host Network
• None

• It acts as a reverse proxy
• It can act as application-level load balancer
• Less attack surface
• Headers Transformation
• Great at serving static assets
• SSL/TLS
• Logging