When most business applications were monolithic, their resilience was never easy. However, considering how the apps run in 2025 and what you’ll expect from them, maintaining a monolithic app was definitely easy.
At the time, IT staff had a finite set of criteria to improve application resilience. The change rate for applications and their infrastructure has been very slow. Today, the requests we place on our apps are different, with more and faster rates of change.
There are even more applications. According to IDC, there is likely to be another billion people in production by 2028, many of which will run on cloud-native code and mixed infrastructure. The increased expectations of service for technical complexity and responsiveness and quality have led to a very complicated question resilience.
Multidimensional elements determine the dimensions that fall within different areas of app resilience, modern corporate responsibility. Code quality is categorized into development teams. The infrastructure may depend on your system administrator or DevOps. Compliance and data governance personnel have their own needs and regulations, including cybersecurity experts, storage engineers, database administrators, and dozens more, as well.
By defining what constitutes resilience by who is asking, using multiple tools designed to ensure app resilience – it’s a small wonder that there are many tools that work to improve and maintain play resilience at any time in modern companies.
Therefore, it is nearly impossible to determine resilience across the entire enterprise portfolio. The monitoring software is a siloed and there is no single pane of reference.
IBM’s concert resilience attitude simplifies the complexity of multiple dashboards, normalizes different quality judgments, breaks down data from different silos, and integrates different objectives of monitoring and repair tools.
Advances Jennifer Fitzgerald (June 4-5, June 4-5, Santa Clara Convention Center), Product Management Director at IBM Observability, presented the concert’s resilience attitude solutions, their purpose and spirit. In the latter, she distinguishes it from other tools.
“Everything we do is based on the application. It reduces application health and performance, and application risk factors.”
An app-centric approach means bringing together different metrics in the context of your desired business outcomes, answering questions that are important to your organization’s stakeholders.
Do all applications scale? What is the effect of changing the code? Are we overloading or resourced elements of our application? Does your infrastructure support or interfere with application deployment? Are we safe and in line with our data governance policy?
Jennifer says that the resilience attitude at an IBM concert is “a new way to think about resilience. It’s about moving it from manual stitching (of other tools) or a ton of dashboards.” The definition of resilience can be temporary, but Jennifer says it consists of eight non-functional requirements (NFRs).
ObervabilityAvabilityMaintainabilityRecoverabilityScalability -UsabilityIntegritySecurity
NFRs are important anywhere within the organization, with only two or three, perhaps the only remittances in one department. For example, security drops to CISO. But ensuring the best resilience with all of the above is very important across the enterprise. This is a common responsibility to maintain performance, potential and safety excellence.
The attitude of IBM concert resilience is proactive beyond the single glass paradigm, offering different organizations than those offered by different collections of tools. Aggressive resilience arises from the ability to give a resilience score based on multiple metrics, with scores determined by dozens of data points in each NFR. Companies can drift overall or per-app scores when changes are made to their infrastructure, code, and portfolios of applications in production.
“The idea of ​​resilience is that we as humans are not perfect. We make mistakes. But how do we come back? Your application is perfectly performant, always optimal, and happens with the uptime required. But the problem breaks something. Surge in demand, (and) unexpected events,” she says.
IBM’s acquisition history points to some of the free elements of the Concert Resilience Astute Solution. For example, Instana, Turbonomic, etc. for full stack observability. But the whole is greater than the sum of the parts. With an AI-driven continuous assessment of all the elements that make up an organization’s resilience, there is one place where decision makers and IT teams can evaluate, manage and configure a full-stack resilience profile.
The IBM portfolio of solutions focused on Resilience helps teams see when resources change. It is possible to ensure that the necessary resources are allocated only when needed, and that the system will automatically shrink if it is not. This kind of business and cost-centric feature is at the heart of app-centric resilience, meaning that businesses are constantly optimizing their resources.
Ensuring all aspects of app performance and resilience is a factor of cost. Throwing additional resources into a low-performing application (or its support infrastructure) is not a viable solution for most organizations. With IBM, organizations gain the ability to scale and grow, safely add or iterate apps, either in the cloud or on-premises, without necessarily investing in new provisioning. Additionally, you can see how change affects resilience. They make the most of what is available and win their abilities. This is while achieving the best performance, responsiveness, reliability and uptime across the enterprise application portfolio.
Jennifer said, “There are many different things that can affect resilience. It was very difficult to measure. An application has so many different layers, no matter how it’s built, with just that resource. But changes to the code can affect multiple apps. And.”
For more information about IBM’s work, you can make today and tomorrow’s applications resilient.
