In 2013, APMdigest published a list called 15 Top Factors That Impact Application Performance. Even today, this is one of the most popular pieces of content on the site. And for good reason – the whole concept of Application Performance Management (APM) starts with identifying the factors that impact application performance, and then doing something about it. However, in the fast moving world of IT, many aspects of application performance have changed in the 3 years since the list was published. And many new experts have come on the scene. So APMdigest is updating the list for 2016, and you will be surprised how much it has changed.
Part 5 is the final installment of the list of top factors that impact application performance.
27. CODE INTEGRATION
As application topologies become more and more distributed, the need for seamless code integration between applications in new releases has become a significant factor in application performance. This is especially true in the case of expanding IT departments when new employees are not always familiar with the application topologies and dependencies in an organization.
Founder & CEO, Correlsense
28. PACE OF INNOVATION
Developers are reacting to unrelenting pressure from the business to implement more business functionality in less time, at a lower cost (of development) and to then evolve that code more frequently. These pressures have caused there to be a tremendous amount of innovation in process areas like Agile and DevOps, and in new languages (PHP, Python, Ruby, Node-JS) that collectively improve developer productivity. But all of these process and technology improvements abstract the developer from the performance characteristics of their code. Docker is just the latest example of this. So the number one factor that impacts application performance is that the pace of innovation in the application stacks in response to business pressures makes measuring and ensuring application performance more difficult. This is THE challenge that the APM vendors must address
29. LACK OF TESTING
Not testing performance early in development and not testing it later in production. Today's tools make it easier to "shift-left" moving performance testing into the development cycle so that all new code can have not only unit, smoke, and functional tests, but also performance tests that will detect performance regressions and defects before the code becomes part of the project. Allowing code that performs poorly into a project increases the cost to address this defect later. Adding performance testing as a ‘shift-right' into production ensures that the production system truly can scale and perform well when demand is higher than a development or pre-prod test would simulate. Testing in production also allows testing third-party components as a part of an integrated performance load test. You don't want a third-party feature to be the blocking item that can't perform at scale.
Sr. Evangelist, SOASTA
The biggest factor that impacts application performance is a lack of experience, which includes knowledge. Performance (meaning transactional performance and scalability) gets plenty of lip service, but how many people really test for performance at every build? Think about a scalable and fast architecture from day 1, from the messaging platform to the backend to the use of Angular to the load balancers: Everything has an impact. A culture of testing at every build, and setting clear SLA's drives true performance. There is no way around it.
30. INEFFICIENT COMMUNICATION
Over the past decade, IT Organizations have heavily invested in APM and UEM solutions to become aware of potential performance issues even before consumers of the service felt the pain. New generation APM tools go even further with infrastructure discovery, analytics and deep code analysis to refine and speed up the diagnosis process when something goes wrong. This is all good, but it must be recognized however, that these same organizations tend to spoil all these efficiency gains because of immature communication processes. I believe that no matter how fast IT becomes aware of an application performance issue, today, the top factor that impacts application performance and customer experience is really the ability or inability for the IT organization to respond quickly enough and prevent the issue from getting bigger and the performance from deteriorating even more.
Senior Director of Product Marketing, IT Alerting & IoT, Everbridge
Numerous factors can impact application performance - a mistake in design, application defects, insufficient capacity and many others. However, for each of such factors to impact the application, a change should happen. Application, infrastructure, data, workload or capacity – something should change for performance to deteriorate. Hence, the top factor that impacts application performance is a change. To ensure maximum performance it is critical to know "what's changed?” and be able to detect early changes that are causing negative impact. Today, most application performance management tools still mainly focus on application transaction performance and availability. Leading vendors started to explore application logs looking for additional information about application behavior. Change is a key missing piece required to manage application performance. Change detection, change correlation with performance events, and risk assessment of changes are critical capabilities IT Operations needs to become truly proactive in maintaining optimal application performance.
32. UNKNOWN UNKNOWNS
From reading APM reviews on IT Central Station, I see that it is a common theme that an "unknown unknown" is what most concerns IT and DevOps managers. Examples of these "unknown unknowns" that impact app performance include factors such as the way an application responds to an unanticipated application behavior (e.g. "80% of users are coming from mobile devices!"), user behavior (e.g. "We didn't expect users to keep hitting that button.") and/or load (e.g. "Traffic spike of 600% during the summer!?").
Founder and CEO, IT Central Station
Modern complex systems are easy to develop and deploy but extremely difficult to observe. Their IT Ops data gets very messy. If you have ever worked with modern Ops teams, you will know this. There are multiple issues with data, from collection to processing to storage to getting proper insights at the right time. I will try to group and simplify them as much as possible and suggest possible solutions to do it right ...
In Agile, development and testing work in tandem, with testing being performed at each stage of the software delivery lifecycle, also known as the SDLC. This combination of development and testing is known as "shifting left." Shift left is a software development testing practice intended to resolve any errors or performance bottlenecks as early in the software development lifecycle (SDLC) as possible ...
Overwhelmingly, business leaders cited digital preparedness as key to their ability to adapt, according to an in-depth study by the Economist Intelligence Unit (EIU), looking into how the relationship between technology, business and people evolved during the COVID-19 pandemic ...
Robotic Data Automation (RDA) is a new paradigm to help automate data integration and data preparation activities involved in dealing with machine data for Analytics and AI/Machine Learning applications. RDA is not just a framework, but also includes a set of technologies and product capabilities that help implement the data automation ...
There is no one-size-fits-all approach to changing the experience of employees during a pandemic, but technological innovation can have a positive impact on how employees work from home as companies design their digital workspace strategy. The IT team supporting this shift needs to think about the following questions ...
Downtime. It's more than just a bar on the Rebel Alliance's base on Folor. For IT Ops teams, downtime is not fun. It costs time, money and often, user frustration. It takes more than the Force to handle incidents ... it takes an intergalactic team. An effective incident management team is made up of people with many different skill sets, styles and approaches. We thought it would be fun to map the heroes of IT Ops with Star Wars characters (across Star Wars generations) based on their traits ...
Vendors and their visions often run ahead of the real-world pack — at least, the good ones do, because progress begins with vision. The downside of this rush to tomorrow is that IT practitioners can be left to ponder the practicality of technologies and wonder if their organization is ahead of the market curve or sliding behind in an invisible race that is always competitive ...
According to a new report, Digital Workspace Deployment & Performance Monitoring in the New Normal, 82% of respondents had changes in their digital workspaces due to the pandemic ...
There are a few best practices that DevOps teams should keep in mind to ensure they are not lost in the weeds when incorporating visibility and troubleshooting programs into their systems, containers, and infrastructures. Let's dive into these best practices ...