What makes experience monitoring more challenging with modern apps?

Modern apps leverage infrastructure services which allow connected apps to perform at a global scale.

  • CDN (Content Delivery Network) distribute contents closer to all users at a global scale, as a service
  • Client side rendering. Instead of providing all resources from the server side, JavaScripts are placed in the original pages. These scripts are locally executed by the user’s browser. This JavaScript loads the content and makes sure it is rendered properly from the browser. This enables richer interactions, faster rendering once the scripts are loaded. Most popular web apps rely on frameworks like ReactJS, VueJS and Angular for this.
  • Single page web applications (SPAs). These JavaScript frameworks allow web applications where the content of a single page can be dynamically rewritten instead of loading pre-rendered pages from the server. The concept of browsing from one page to another disappears and more responsive applications become possible. Once the CSS, main files and the javascripts are loaded, the only exchanges between the client and the server are made through APIs (using Ajax calls and Json for example).
  • Edge computing: this consists in distributing the computation and data storage closer to users to accelerate the application rendering. The main difference with CDNs is the fact that it is the computation and not the data storage which is moved closer to users.

The use of edge / cloud computing, CDNs and client side rendering makes experience monitoring more difficult.

While these technologies vastly improved the experience and the possibilities of web applications, they also bring new challenges from a performance monitoring standpoint:

  • Cloud / Edge computing. relying on technologies like Infrastructure as a Service /Platform as a Service, reduces your level of control and your options to instrument your application. As an example, you cannot place an agent on a PaaS and you must live with the native instrumentation provided by your cloud provider or instrument your code.
  • CDN service / edge hosting. Distributing your resources in 3rd party infrastructure make the monitoring of their access by your users more difficult.
  • Single Page Application and client side-rendering. Traditional real user monitoring are designed for server side rendered applications.
  • End to end path complexity. Depending on the users location, it becomes very hard to understand all the chain which is followed to access all the application resources.

Which DNS server is used and what is the resolution time and result?
Resolving into a resource located where? How do the location, path and performance vary through time?

Understand experience for modern apps requires a new approach to performance monitoring

  • Measure experience from the point of view of every user
  • Consider the impact of every infrastructure service involved (CDN, 3rd party, edge computing, PaaS services)
  • Reflect experience for SPAs and client side rendered functions.

Give your team full end to end visibility of modern app digital experience

Kadiska tracks the overall experience of modern apps regardless of the way they are hosted, distributed and rendered.

  • Wherever you host your resources: all the requests from all the users will be tracked.
  • In whichever way your application is run: whether your application is rendered on the server or on the browser, it will be tracked.
  • Throughout the globe, Kadiska’s performance stations will test all the resources called by your real users (DNS servers, network path to all your resources – edge, CDN, cloud or data centers).

With a service that self installs instantly, is completely non intrusive!

Showing the digital experience of modern apps at a glance

Sounds interesting?

Find 20 minutes to discuss your requirements and discover Kadiska’s capabilities.

Let's get in touch