Whether you consider the first generation of APM or the updates that followed for SOA and microservices, the most basic premise of the tools remains the same — PROVIDE VISIBILITY.
"Distributed" was The Word for 2010
Eventually, new application platforms appeared, and Service Oriented Architecture became the model of choice for building enterprise applications. This helped development and operations teams react faster to market needs and build software faster — but the centralized aspect of monolithic applications disappeared, which created performance management challenges.
Developers were able to build applications encompassing more complex processes. SOA was also a catalyst for development strategies that focused on re-using building blocks and beginning to think of organizations as software factories.
The biggest difference between standard J2EE applications and SOA applications can be summed up in one word — Distributed.
Without a singular central core of business logic that gated all requests, the first-generation tools struggled. All those visibility holes they filled in reappeared in distributed environments.
New features became a requirement for distributed applications — with component discovery and mapping the most visible of those, with some sampled tracing and production profiling as well.
These requirements were the basis of a new — and very successful — generation of tools that were purpose built to deal with distributed applications. These tools allowed for flexible architectural design, provided end-to-end mapping and could be configured to understand the different relationships that could exist in a complex distributed app.
The Word for the Twenties? Ephemeral — Yes, Ephemeral
Dictionary.com defines ‘ephemeral' as "lasting a very short time; short-lived; transitory."
Why is ephemeral the defining word for APM this decade? To understand, we have to back up just a bit.
A few years ago, application technology shifted again with the introduction of containers and microservices. Unlike previous introductions of new application technologies, containers became a smashing hit — FAST — even in the enterprise. What took Java almost a decade to achieve (enterprise acceptance and prevalent usage), containers achieved in 2-3 years.
One of the more endearing container concepts is the ability to spin up new containers whenever needed to deliver more scalable applications through on-demand resources.
Yes, Containers — But Microservices, Too
If containers was the only recent application breakthrough, that would be ephemeral enough, but containers are just the beginning of the dynamic nature of modern applications.
The microservices-based architecture enables a new way of thinking about designing, building, deploying and updating application components, becoming even more distributed and changing the way technology platforms are chosen and used.
But Wait, There's More — or is it Less?
As if that weren't enough, now consider functions running on Serverless platforms. The most recognizable is AWS Lambda, but each cloud provider has a version of Serverless that provides the least amount of possible resources needed to execute a small piece of repeatable code
So the answer to the question "what's ephemeral about modern applications?" is "Well — everything!"
Managing performance of such dynamic applications requires the automated visibility introduced by the first generation of tools, the dynamic mapping associated with the second generation, PLUS the understanding that change is constant.
And that means being able to do some things in real time — detect new or updated infrastructure, detect changes to the application code, and trace all requests since each one is probably different. And last, but not least, is the ability to provide immediate feedback whenever an update occurs.
After all, the importance and need for Application Performance Management tools is the same as it was twenty years ago — to help optimize the user experience by minimizing service impacts and solving problems quickly when they occur.
It's more important today to a much broader set of customers because applications ARE the business in many cases. The nice thing is that new APM vendors come along to solve new problems — so that you can keep your applications running at optimum levels.
The Internet played a greater role than ever in supporting enterprise productivity over the past year-plus, as newly remote workers logged onto the job via residential links that, it turns out, left much to be desired in terms of enabling work ...
The world's appetite for cloud services has increased but now, more than 18 months since the beginning of the pandemic, organizations are assessing their cloud spend and trying to better understand the IT investments that were made under pressure. This is a huge challenge in and of itself, with the added complexity of embracing hybrid work ...
After a year of unprecedented challenges and change, tech pros responding to this year’s survey, IT Pro Day 2021 survey: Bring IT On from SolarWinds, report a positive perception of their roles and say they look forward to what lies ahead ...
One of the key performance indicators for IT Ops is MTTR (Mean-Time-To-Resolution). MTTR essentially measures the length of your incident management lifecycle: from detection; through assignment, triage and investigation; to remediation and resolution. IT Ops teams strive to shorten their incident management lifecycle and lower their MTTR, to meet their SLAs and maintain healthy infrastructures and services. But that's often easier said than done, with incident triage being a key factor in that challenge ...
Achieve more with less. How many of you feel that pressure — or, even worse, hear those words — trickle down from leadership? The reality is that overworked and under-resourced IT departments will only lead to chronic errors, missed deadlines and service assurance failures. After all, we're only human. So what are overburdened IT departments to do? Reduce the human factor. In a word: automate ...