I have an application with 2 backend servers(512Mb droplet) which is normally idle except for 4AM to 4PM UTC. The load is getting higher each day as the user continue to increase.
I am thinking to automatically boot another droplets from an image if the certain threshold is met and kill those droplets and leave X droplets by default if the traffic is back to normal again to save $$.
I’m using nginx as load balancer… As an example below the upstream backend IPs are hardcoded in my load balancer config. I am planning to update this config after each droplet is booted up and ready then restart nginx.
upstream backend {
server web-sms01:80
server web-sms02:80 ;
}
Do you guys have better way of doing this? My method is a bit funny I think. :)
- Resizing a droplet is not an option because 1 minute downtime is very long for my users.
- AWS ELB is not an option for now… :)
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
