How to configure and maintain a server overload page with whales?

We have a fairly large member site configured on AWS using a medium high-performance server. Most of the time it works at a very low power (~ 3%), but once a week we send a newsletter to our members with opportunities. Within minutes after the newsletter, server load increases (sometimes to over 100%) with members trying to access the site.

In the long run, we will restructure the system, but at the moment I want to add an overflow server that will serve users for several minutes while this happens.

I could not find any good tips on setting up routing for this type of thing. Any ideas?

Thank!

+3
source share
2 answers

Why not use the elasticity of load balancing as well as automatic scaling instead?

This will allow you to compare the number of servers with actual use. Most of the week you will not pay for 97% of the unused capacity, and during the periods of the newsletter you will have enough opportunities to enter the system and purchase from you.

+3
source

There is a post on the Amazon Web Services Blog explaining how to do this. It puts the switch page to another resource on S3, which is easy to maintain and cheap.

Create a backup site using routing 53 DNS routing and S3 website hosting

0
source

All Articles