18 Ways to Ensure Application Performance Before Rollout - Part 3
February 13, 2015

APMdigest asked experts from across Application Performance Management (APM) and related markets for their recommendations on the best ways to ensure application performance before app rollout. This final set of six recommendations covers topics including the development environment and deployment.

Start with Part 1 of this list

Start with Part 2 of this list

13. REPLICATION OF REAL-WORLD PRODUCTION CONDITIONS

Understand the logical complexity of your application, especially round trips at various levels of abstraction. Test the most logically complex components with production-like latency, reasonably complex inputs, and realistic load. Ideally, use the same profiling tool you would use in production, and make sure it can find meaningful problem correlations at scale. A top methods list will only show you where your time went processing your synthetic load.
Joe Rustad
Manager, Software Development & Architecture, Dell Software

Networked delivered applications are pervasive in todays businesses and its essential that we give developers and testers environments that that are "fit for the purpose" i.e. they accurately reflect the network an application is expected to run in - this ensures a much more robust application is produced and can substantially shorten the delivery time. Developers and testers can utilize industry standard tools such as Network Emulators which replicate the target networks and network conditions, eliminating any unwanted surprises when a new application is rolled out into the production environment.
Jim Swepson
Pre-sales Technologist, iTrinegy

14. CONTAINER TOOLS

Container tools provide the easiest, most effective and secure approach for ensuring application performance prior to rollout – not to mention, most affordable. An added level of virtualization that conveniently packages everything together, containers enable DevOps to decouple applications from underlying hardware and IT infrastructure, which among other things, make apps highly portable, as well as easier to share, test, deploy, fine-tune for performance and manage.
Don Boxley
CEO and Co-Founder, DH2i

15. BI-MODAL IT

Operations teams should adopt a bi-modal IT structure to optimize application release cycles and updates. A bi-modal structure focuses on increasing the application performance, speed and agility of operations, allowing for scaling applications and businesses without creating a shadow IT environment. By utilizing containerization to provide independent work spaces, applications can be optimized to increase performance. A bi-modal IT structure allows for a smooth development and deployment process from the onset.
Charlie Key
Founder of Modulus, a Progress company

16. COLLABORATION AND COMMUNICATIONS INFRASTRUCTURE

Investing time into developing a coherent Collaboration and Communications Infrastructure (CCI) plan that outlines a set of procedures and policies for IT and end-users to follow is vital to ensuring top service performance. Having a CCI strategy in place will enhance enterprise IT collaboration capabilities and help assure the performance and availability of collaboration and communications services in the production environment.
Mike Segal
Director of Solutions Marketing, NetScout Systems

17. APPLICATION DIAGNOSTICS

Developers must go beyond instrumenting their apps to provide diagnostics like crash reporting, service monitoring, and transaction trace.
Mike Marks
Chief Product Evangelist, Aternity

18. INCREMENTAL DEPLOYMENT

Successful rollouts are all about manageability. First, deploy in phases (vs. a big bang approach), so you can learn as you go and change course as needed, including rolling back. Next, and complementary to the phased rollout, have key performance metrics from production environment against which you can compare in the pre-production environment and during each step of the deployment. For todays complex application systems, this is best accomplished with cross-tier transaction response times. The ability to compare application performance snapshots before and after deployment is also extremelly helpful.
Anand Akela
Director, APM Product Marketing, AppDynamics

Consider deploying the application to a limited number of test users in each site to get some preliminary testing done. Set expectations for how the application should perform and give users adequate time to acclimate and validate the new application as part of their workflow. How are users receiving the new application? What is the user experience like? Are there any issues that need to be resolved immediately?
Bruce Kosbab
CTO, Fluke Networks

Bruce Kosbab Blog: 9 Key Performance Considerations for App Rollouts

The Latest

August 15, 2018

Microservices are a hot topic in IT circles these days. The idea of a modular approach to system building – where you have numerous, smaller software services that talk to each other instead of monolithic components – has many benefits ...

August 13, 2018

Agile is expanding within the enterprise. Agile adoption is growing within organizations, both more broadly and deeply, according to the 12th annual State of Agile report from CollabNet VersionOne. A higher percentage of respondents this year report that "all or almost all" of their teams are agile, and that agile principles and practices are being adopted at higher levels in the organization ...

August 09, 2018

For the past 13 years, the Ponemon Institute has examined the cost associated with data breaches of less than 100,000 records, finding that the costs have steadily risen over the course of the study. The average cost of a data breach was $3.86 million in the 2018 study, compared to $3.50 million in 2014 – representing nearly 10 percent net increase over the past 5 years of the study ...

August 08, 2018

Hidden costs in data breaches – such as lost business, negative impact on reputation and employee time spent on recovery – are difficult and expensive to manage, according to the 2018 Cost of a Data Breach Study, sponsored by IBM Security and conducted by Ponemon Institute. The study found that the average cost of a data breach globally is $3.86 million ...

August 06, 2018

The previous chapter in this WhiteHat Security series discussed dependencies as the second step of the Twelve-Factor App. This next chapter examines the security component of step three of the Twelve-Factor methodology — storing configurations within the environment.

August 02, 2018

Results from new Forrester Consulting research reveal the 20 most important Agile and DevOps quality metrics that separate DevOps/Agile experts from their less advanced peers ...

July 31, 2018

Even organizations that understand the importance of cybersecurity in theory often stumble when it comes to marrying security initiatives with their development and operations processes. Most businesses agree that everyone should be responsible for security, but this principle is not being upheld on a day-to-day basis in many organizations. That’s bad news for everyone. Here are some best practices for implementing SecOps ...

July 30, 2018

While the technologies, processes, and cultural shifts of DevOps have improved the ability of software teams to deliver reliable work rapidly and effectively, security has not been a focal point in the transformation of cloud IT infrastructure. SecOps is a methodology that seeks to address this by operationalizing and hardening security throughout the software lifecycle ...

July 26, 2018

Organizations are shifting away from traditional, monolithic architectures, with three-quarters of survey respondents delivering at least some of their applications and more than one-third delivering most of their applications as microservices, according to the State of DevOps Observability Report from Scalyr ...

July 24, 2018

What top considerations must companies make to ensure – or at least help improve – Agile at scale? The following are key techniques and practices to help accelerate Agile delivery rollouts and scale Agile and DevOps in the Enterprise ...

Share this