Cloud Server Use Case: Seasonal Capacity
Table of Contents
- Use Case: Seasonal Capacity
- Scenario 1: Stand-Alone Database Server
- Scenario 2: Off-Peak Traffic
- Scenario 3: Preparing for Peak Traffic
- Scenario 4: Post-Holiday Drop-Off
The 1&1 Cloud Server platform is an excellent choice for websites and applications which need to scale in order to accommodate seasonal traffic. In this use case we will discuss how a user with a seasonal website can use 1&1 Cloud Servers to their advantage.
Use Case: Seasonal Capacity
The following examples revolve around a user with a seasonal e-commerce website. The site sells Halloween decorations and costumes, and experiences very low traffic 10 months out of the year. However, traffic begins to grow at the beginning of September, and peaks through the month of October. By the beginning of November, traffic has dropped off again.
This user needs an affordable way to manage the predictable influx of traffic. Their site needs to be fast and responsive for visitors during the Halloween season, but the user does not want or need to pay top dollar for excess capacity in their system for the other 10 months of the year.
Scenario 1: Stand-Alone Database Server
Like most e-commerce sites, the user's site is database-driven. In order to create the most efficient setup, they will first move their database to its own Cloud Server. This has several advantages:
- It allows them to manage capacity on the database server independent of what is happening with the web servers.
- It isolates the database from traffic on the web servers, so that the database is always operating at peak efficiency.
- It allows them to easily "plug in" and "unplug" Cloud Servers from the database as needed.
- It offers the potential of cloning the database onto multiple servers and using load-balancing to maintain optimal traffic to the database.
Scenario 2: Off-Peak Traffic
During the off-peak months (November through August) the user has one Cloud Server which functions as the web server. This server connects to the single database server to run the e-commerce site.
With only two Cloud Servers for ten months of the year, the user's costs are kept low.
Scenario 3: Preparing for Peak Traffic
At the end of August, the user begins preparing for the September traffic increase. They add several new Cloud Servers to function as web servers for the Halloween shopping season.
To make this process easy, the user simply clones their existing web server. Learn more about this process in our article Cloning a Server.
To distribute traffic between the new web servers, the user sets up a Load Balancer. Learn how to set up and use a Load Balancer in our community articles on this topic.
Scenario 4: Post-Holiday Drop-Off
After Halloween has passed, the user deletes their unnecessary web servers. Because there is no cost for the Load Balancer, they decide to leave it in place in order to simplify their ramp-up process next year.