Avoiding site downtime: how to plan for high availibility


The nature of a mission-critical website is that it cannot fail. Public organisations of all sizes depend on their site being up in order to meet their goals and deliver citizens the consistent, high quality services they expect, whenever they need it most.

As the government’s Digital by Default Service Standard explains:

“The expectation when using an online service is that it’s available 24 hours a day 365 days a year. This is one of the advantages of shifting services online, people can transact with you when it suits them, not just when your office or call centre is open. But achieving good uptime for a service takes planning and good design.”

However, some large organizations haven’t managed to implement the right approach that will keep their site up during critical times. There are numerous examples of high-profile digital properties that have suffered due to traffic spikes that were planned for, but drastically underestimated.

It may seem obvious, but it’s worth thinking about why high availability matters. Understanding the risks and costs involved is an important part of determining the need to protect the availability of your site. In short, having a high availability solution in place could spare you a major headache – and also avoid incurring significant costs.

A new eBook from Acquia, Global Reliability for Sites Too Big to Fail, explores some of the reasons to plan for high availability and outlines a number of best practices to follow when engineering your hosting solution.

From identifying risks and threats and determining availability requirements, to monitoring your sites and systems and testing recovery procedures, the eBook provides a comprehensive guide for anyone within local or central government who is involved in providing citizen-centric digital services.

Download the full eBook below to find out more about how to provide high availability for critical systems that cannot afford downtime:

  • This field is for validation purposes and should be left unchanged.

Related reading