Monitor. Resolve. Prevent.

Alois Reitbauer

Subscribe to Alois Reitbauer: eMailAlertsEmail Alerts
Get Alois Reitbauer via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Alois Reitbauer

  The dynaTrace AJAX Edition has been out there as an Alpha for a couple of weeks. It gave you the first impression what was to come. All the feedback we have received (like that from Steve Souders, and all that has come in via the contact form and the online forum) in that time made it possible to improve the tool from its early versions to its first "official" release version. In this article I'll discuss why dynaTrace Labs built the AJAX Edition, which problems it solves and how to use it in an example with Google maps. Why dynaTrace AJAX dition - and why for free? At dynaTrace, we see the paradigm shift of web applications with our clients as well as in the industry where the browsers and their runtimes (JavaScript, DOM) become application platforms. The rise of frameworks like jQuery, GWT, YUI, DoJo, ... make it easier to build Web 2.0 applications - but it has ... (more)

Performance Considerations in Distributed Applications

Java Developer Magazine on Ulitzer Distribution and communication between applications and services is a central concept in modern application architectures. In order to profit from distribution you have to keep some basic principles in mind – otherwise you can easily run into performance and scalability problems. During development these problems often do not surface.  Then suddenly in load testing or production you might then realize that your chosen software architecture does not support the required performance and scalability requirements. In this post we will look at major... (more)

Applying Maslow’s Pyramid to Application Performance

This time I take an a bit of an unconventional approach towards defining performance management. The idea for this article came through a number of customer engagements, where the same question came up over and over again: “How do we start with Application Performance Management and what should we do?” Over time I developed a simple model which I called the performance management pyramid. The basic idea is to assign performance management activities to several levels. Each level serves a specific need and builds on top of the lower ones. Just like a building it starts with the b... (more)

The Proactivity of Troubleshooting

Troubleshooting of performance problems is very often - if not almost always - viewed as a reactive activity. Frankly, I have often seen it done in such a reactive fashion as a firefight; however, effective troubleshooting should build upon a solid diagnostic process. If you handle troubleshooting as if firefighting rather than based on solid diagnosis, this inevitably is a sign you have failed to take the right proactive measures. The goal of troubleshooting is to resolve an immediate performance problem - ideally yesterday. As some might expect this does not start when the probl... (more)

Seven Rules to Improve Your Application Performance Practices

In this article I discuss the seven most important steps to improve your application performance practices. These simple-to-follow practices will help you to improve the way you deal with application performance. Besides eventually improving the performance of your applications it will help you to avoid playing the classical blame game which normally happens when something goes wrong Rule 1 – Understand the Application While this may sound trivial and the most obvious thing to do – reality paints a different picture. Most failing application performance management processes orig... (more)