After spending years and millions of dollars deploying a web-based, mission-critical application, the last thing you want to hear is that the rollout is going poorly due to performance issues. But, as organizations continue to migrate to browser-based deployments, that’s often exactly what happens.
While users enjoy the virtually ubiquitous access to applications—regardless of location—enabled by browser-based clients, they are dissatisfied with the performance of web-based applications versus their old fat-client counterparts.
Combining reduced performance with an increasingly distributed workforce introduces yet another set of factors that contribute to even more disappointing performance. A plethora of network and application issues coalesce into a perfect storm, impeding performance and hampering the usability of multi-million dollar investments. Adding a dose of Web 2.0 technologies to the enterprise application mix only exacerbates the decline in performance for remote and mobile users.
Most of the IT and applications managers experience anxiety related to application performance and report physical aches and pains along with their unease. These fears are not ungrounded, as there are a myriad of issues that negatively impact the performance of applications.
Network, client, and data center issues all play a role in how well your web applications perform. An application delivery network can act to alleviate the challenges inherent in delivering web applications over a widely variable network.
Application Delivery Challenges
Understanding the types of applications being delivered can greatly improve the ability to optimize and improve their overall performance by identifying the challenges particular to different types of applications.
In case of Web applications, it combines the issues arising from constantly changing content with increasing volume and the connection management problems inherent in service oriented and component-based architectures.
While enabling syndication of content, providing personalization, and building an increasingly community-driven web presence is in high demand today, Web applications can have a detrimental effect on the underlying infrastructure. Often, Web 2.0 applications consume more resources per user than their legacy counterparts due to the connection-heavy technologies underlying Web applications such as Wikis, blogs, mash-ups, Rich Internet Applications (RIA), and discussion-based forums.
These emerging applications are highly dynamic and constantly changing, creating challenges in formulating disaster recovery plans as well as performing backups and replication on a regular basis. The timing, amount of data, and bandwidth available for replication and backup efforts all affect an organization’s confidence that their disaster recovery plans can effectively be carried out.