Ticket master for example. Whenever there’s a high volume of traffic, the website crashes or experiences problems. Surely they know that there’s going to be a huge surge in traffic all at once? Can they not design the website to cope with the increase in demand and function like normal?
In: 5
Because it’s a hardware issue.
A website sits on the server. Whoever owns the website either owns a server to put the website on or pays someone to keep the website on their server. Larger websites can have multiple servers, but that costs more because it requires more hardware. When a lot of traffic hits the website at once, the server is operating at maximum capacity, with requests for information constantly coming in, and it can only fulfill those requests so fast. When there’s more requests than the server can handle, it can crash. And even before that, the website’s performance will be very slow.
The only real solution is to get more servers, and that can’t be done instantly, and requires that data from existing servers be copied over, which can’t be done while they’re full of traffic.
Ticket master in particular, is limited in this capacity, because it needs to keep track of which tickets have been reserved, which can’t update instantly across servers. Something like YouTube can give out videos from multiple servers, but no resource is being reserved in that case. Ticket master would need on server keeping track of which tickets have been sold before anyone can attempt to buy one. That’s the bottle neck.
Latest Answers