ESPN made news headlines this past weekend – the bittersweet kind. Unfortunately, the news highlighted that ESPN's fantasy football app was crashing, on the first Sunday of the NFL season. Where's the "sweet" part? The crash likely signals a huge amount of user popularity.
We see these types of stories often during so-called "surge" events, like when Black Friday takes down a retailer. Why? Often, it's the database that's been swamped in the process.
The application-to-database connection is fragile, because applications have to directly tie into the database and the coding of the app must match the database infrastructure. For example, if the database has multiple database servers that can all respond to an inbound request, the application needs to know which type of server to send its request to. While those changes can ensure a better response time, the work isn't trivial – a programmer must go through hundreds of thousands of lines of code to program how to handle reads vs. writes – and it can lead to errors.
Any recent changes by ESPN to increase database capacity or update the app could jeopardize that fragile connection. If ESPN recently modified the application to talk to different database servers, for example, the team might have accidentally introduced a "bad" query that the database can't handle or might have changed how the application talks to the database and broken that connection.
Organizations that are anticipating a surge in traffic have a number of best practices they should follow to ensure a smooth experience for their customers, including:
1. Freezing code early
Despite the understandable desire to make the app or site as current as possible, it's essential for engineering to force a code freeze many weeks before the "go live" date. Quality assurance (QA) and other testing require adequate time to ensure the updated site or app is working as needed.
2. Load testing
A big part of that testing work needs to come in the form of load testing. After a QA team has performed functional testing – that is, does each feature work – the next step is to see how the code performs when it's swamped with traffic. The key is to perform this load testing with traffic that's as close to production traffic as possible.
3. Increasing resiliency at the data tier
The lifeblood of any app or site is data; without it, you're down. To build in resiliency at this layer, organizations need to employ techniques such as database scale out to have multiple copies of the data available and database load balancing to ensure traffic is serviced by the fastest-responding server to the user.
4. Enabling redundancy in all network services
Beyond the data tier, organizations need to make sure the rest of the technology stack has all the redundancy built in as possible. Web server infrastructure and web load balancers are critical, as is network redundancy into both the web farms and the database server clusters. If you're hosting the app or service in the cloud, ensure a redundant version is available in an alternate cloud region.
Michelle McLean is VP of Marketing at ScaleArc.
The Latest
If you were lucky, you found out about the massive CrowdStrike/Microsoft outage last July by reading about it over coffee. Those less fortunate were awoken hours earlier by frantic calls from work ... Whether you were directly affected or not, there's an important lesson: all organizations should be conducting in-depth reviews of testing and change management ...
In MEAN TIME TO INSIGHT Episode 11, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses Secure Access Service Edge (SASE) ...
On average, only 48% of digital initiatives enterprise-wide meet or exceed their business outcome targets according to Gartner's annual global survey of CIOs and technology executives ...
Artificial intelligence (AI) is rapidly reshaping industries around the world. From optimizing business processes to unlocking new levels of innovation, AI is a critical driver of success for modern enterprises. As a result, business leaders — from DevOps engineers to CTOs — are under pressure to incorporate AI into their workflows to stay competitive. But the question isn't whether AI should be adopted — it's how ...
The mobile app industry continues to grow in size, complexity, and competition. Also not slowing down? Consumer expectations are rising exponentially along with the use of mobile apps. To meet these expectations, mobile teams need to take a comprehensive, holistic approach to their app experience ...
Users have become digital hoarders, saving everything they handle, including outdated reports, duplicate files and irrelevant documents that make it difficult to find critical information, slowing down systems and productivity. In digital terms, they have simply shoved the mess off their desks and into the virtual storage bins ...
Today we could be witnessing the dawn of a new age in software development, transformed by Artificial Intelligence (AI). But is AI a gateway or a precipice? Is AI in software development transformative, just the latest helpful tool, or a bunch of hype? To help with this assessment, DEVOPSdigest invited experts across the industry to comment on how AI can support the SDLC. In this epic multi-part series to be posted over the next several weeks, DEVOPSdigest will explore the advantages and disadvantages; the current state of maturity and adoption; and how AI will impact the processes, the developers, and the future of software development ...
Half of all employees are using Shadow AI (i.e. non-company issued AI tools), according to a new report by Software AG ...
On their digital transformation journey, companies are migrating more workloads to the cloud, which can incur higher costs during the process due to the higher volume of cloud resources needed ... Here are four critical components of a cloud governance framework that can help keep cloud costs under control ...
Operational resilience is an organization's ability to predict, respond to, and prevent unplanned work to drive reliable customer experiences and protect revenue. This doesn't just apply to downtime; it also covers service degradation due to latency or other factors. But make no mistake — when things go sideways, the bottom line and the customer are impacted ...
