HarshPatel

Ahmedabad, Gujarat

Putting It All Together

Now that we have covered all major Docker concepts, in a real-life scenario with our three images:

mongo
mongo-express
our Node.js app

we would run all three together using Docker Compose.

Real-World Architecture

In a real application, we typically have multiple services running together:

text

Node.js App
MongoDB
Mongo Express

Each service runs in its own container.

Using Docker Compose for Full Stack Setup

We can define all three services in a single docker-compose.yaml file.

What Docker Compose Does Here

Creates 3 containers
Assigns them to the same default network
Allows them to communicate with each other
Manages startup and shutdown together

Example Structure

yaml

services:
  mongo:
    image: mongo
    ports:
      - 27017:27017
    environment:
      MONGO_INITDB_ROOT_USERNAME: admin
      MONGO_INITDB_ROOT_PASSWORD: qwerty

  mongo-express:
    image: mongo-express
    ports:
      - 8081:8081
    environment:
      ME_CONFIG_MONGODB_ADMINUSERNAME: admin
      ME_CONFIG_MONGODB_ADMINPASSWORD: qwerty
      ME_CONFIG_MONGODB_URL: mongodb://admin:qwerty@mongo:27017/

  node-app:
    build: .
    ports:
      - 5050:5050
    depends_on:
      - mongo

How Everything Connects

text

User
  ↓
Node.js App (Container)
  ↓
MongoDB Container
  ↑
Mongo Express Container (UI)

Key Concepts Working Together

1. Containers

Each service runs in its own container
Fully isolated runtime environments

2. Networking

All containers are on the same Docker Compose network
They communicate using service names (e.g., mongo)

3. Volumes (if added)

MongoDB data can persist using volumes
Data survives container restarts

4. Docker Compose

Single file manages entire stack
One command to start everything:

bash

docker compose up -d

One command to stop everything:

bash

docker compose down

Why This Setup is Powerful

Instead of manually running multiple commands like:

bash

docker run mongo
docker run mongo-express
docker run node-app

We simply run:

bash

docker compose up -d

Benefits

Easier development setup
Reproducible environments
No manual container management
Works the same across all machines
Ideal for team collaboration

Final Insight

This is exactly how real-world backend systems are structured:

Frontend → Container
Backend → Container
Database → Container
Admin UI → Container

All connected through Docker networking and managed using Docker Compose.

Summary

Multiple containers work together in real applications
Docker Compose connects and manages them
Containers communicate via internal networking
One command controls the entire system
This is the standard approach in modern DevOps workflows

PreviousNext

Putting It All Together

Now that we have covered all major Docker concepts, in a real-life scenario with our three images:

mongo
mongo-express
our Node.js app

we would run all three together using Docker Compose.

Real-World Architecture

In a real application, we typically have multiple services running together:

text

Node.js App
MongoDB
Mongo Express

Each service runs in its own container.

Using Docker Compose for Full Stack Setup

We can define all three services in a single docker-compose.yaml file.

What Docker Compose Does Here

Creates 3 containers
Assigns them to the same default network
Allows them to communicate with each other
Manages startup and shutdown together

Example Structure

yaml

services:
  mongo:
    image: mongo
    ports:
      - 27017:27017
    environment:
      MONGO_INITDB_ROOT_USERNAME: admin
      MONGO_INITDB_ROOT_PASSWORD: qwerty

  mongo-express:
    image: mongo-express
    ports:
      - 8081:8081
    environment:
      ME_CONFIG_MONGODB_ADMINUSERNAME: admin
      ME_CONFIG_MONGODB_ADMINPASSWORD: qwerty
      ME_CONFIG_MONGODB_URL: mongodb://admin:qwerty@mongo:27017/

  node-app:
    build: .
    ports:
      - 5050:5050
    depends_on:
      - mongo

How Everything Connects

text

User
  ↓
Node.js App (Container)
  ↓
MongoDB Container
  ↑
Mongo Express Container (UI)

Key Concepts Working Together

1. Containers

Each service runs in its own container
Fully isolated runtime environments

2. Networking

All containers are on the same Docker Compose network
They communicate using service names (e.g., mongo)

3. Volumes (if added)

MongoDB data can persist using volumes
Data survives container restarts

4. Docker Compose

Single file manages entire stack
One command to start everything:

bash

docker compose up -d

One command to stop everything:

bash

docker compose down

Why This Setup is Powerful

Instead of manually running multiple commands like:

bash

docker run mongo
docker run mongo-express
docker run node-app

We simply run:

bash

docker compose up -d

Benefits

Easier development setup
Reproducible environments
No manual container management
Works the same across all machines
Ideal for team collaboration

Final Insight

This is exactly how real-world backend systems are structured:

Frontend → Container
Backend → Container
Database → Container
Admin UI → Container

All connected through Docker networking and managed using Docker Compose.

Summary

Multiple containers work together in real applications
Docker Compose connects and manages them
Containers communicate via internal networking
One command controls the entire system
This is the standard approach in modern DevOps workflows

PreviousNext

Part 1: Complete Docker One Shot — End to End Guide

Part 1: Complete Docker One Shot — End to End Guide

Putting It All Together

Putting It All Together

Real-World Architecture

Using Docker Compose for Full Stack Setup

What Docker Compose Does Here

Example Structure

How Everything Connects

Key Concepts Working Together

1. Containers

2. Networking

3. Volumes (if added)

4. Docker Compose

Why This Setup is Powerful

Benefits

Final Insight

Summary

Putting It All Together

Putting It All Together

Real-World Architecture

Using Docker Compose for Full Stack Setup

What Docker Compose Does Here

Example Structure

How Everything Connects

Key Concepts Working Together

1. Containers

2. Networking

3. Volumes (if added)

4. Docker Compose

Why This Setup is Powerful

Benefits

Final Insight

Summary