Scaling Web Infrastructure with DigitalOcean Load Balancers and Docker

Basic Load Balancing for a Web System on DigitalOcean

DigitalOcean’s Load Balancer distributes incoming HTTP traffic across a pool of droplet nodes to ensure high availability. This architecture utilizes a Docker-based Nginx and PHP-FPM stack to create a redundant web entry point with minimal configuration.

Why This Matters

In technical reality, single-node deployments represent a critical point of failure where hardware or software crashes halt service entirely. Moving to a load-balanced model transitions infrastructure from fragile single-point systems to distributed environments where traffic is routed through internal private networks, providing horizontal scalability and resilience at a low cost.

Key Insights

• Internal Network Routing: Traffic between the DigitalOcean Load Balancer and droplets occurs over internal IPs, improving security and reducing latency.
• Containerized Stack: Using Docker Compose allows for a portable application environment where Nginx and PHP-FPM are orchestrated as discrete services.
• Rapid Scaling via Snapshots: New server nodes can be added to the load balancer pool in minutes by creating a snapshot of the primary droplet and cloning it within the same region.
• Network Mode Host: The Docker configuration uses network_mode host to simplify communication between the Nginx container and the PHP-FPM service on the droplet.
• Health Monitoring: DigitalOcean automatically monitors node health, only routing traffic to droplets once they are verified as healthy by the load balancer service.

Working Examples

A lightweight PHP script used to verify which backend server is responding to the load balancer request.

<?php echo 'Hi. From ip '.$_SERVER['SERVER_ADDR'];

Docker Compose file for orchestrating the Nginx and PHP-FPM services using host networking.

version: '3.8' services: nginx: image: nginx:alpine container_name: nginx-web network_mode: host volumes: - ./:/var/www/html - ./nginx.conf:/etc/nginx/conf.d/default.conf depends_on: - php-fpm php-fpm: image: php:8.2-fpm container_name: php-app network_mode: host volumes: - ./:/var/www/html

Practical Applications

• High Availability Web Hosting: Deploy multiple droplets across a single load balancer to ensure the application remains online even if one server node fails. Pitfall: Failing to use a shared database or session store will result in inconsistent user data across different nodes.
• Security Hardening: Use DigitalOcean firewalls to restrict droplet access so they are only reachable from the Load Balancer IP. Pitfall: Leaving port 80 open to the public on individual droplets bypasses the load balancer and increases the attack surface.

References:

• https://dev.to/oscar_ricardosncheguti/basic-load-balancing-for-a-web-system-on-digitalocean-2hf7