More and more applications are becoming internet enabled. To optimize operations expenditure, enterprises have started aggressively promoting web sites with self-service capabilities. It could be a simple activity such as gathering information such as case/claim status, submitting claim/service request or paying your bills/buying products online.
As an architect, one of my most critical activity is to regularly monitor my Java based web application’s health during business hours; identify performance bottlenecks and suggest remedial measures. Basically keep the engine humming sweetly without any hiccups. My application is monitored using dynaTrace. dynaTrace has been my trusted partner along with whom I have fought numerous performance related skirmishes and I have come to like it a lot. Recently my organization decided to do an enterprise wide APM roll out of the new kid on the block ‘New Relic‘. The aim of this blog post is to share with all my experiences and observations around the two APM tools, their design philosophies and their differences. My observations are solely in the context of web application performance monitoring, pure Java application monitoring is a completely different ball game.
I have been looking at application performance issues in various shapes and forms since I started doing software development around 15 years back. As I moved up the technology value chain, I started getting called into crisis assignments. Basically there was an application in crisis; it was experiencing performance issues. Could I come over and help address the issue?
In continuation of the ‘Mule Tutorial Series’, this blog post intends to explain the use of all flow control component.
So far the HTTP endpoint demonstrated in this tutorial series had inbound HTTP endpoints. The HTTP endpoint also supports outbound endpoint. This example illustrates two functionalities one displays use of HTTP endpoint as outbound endpoint and second demonstrates the ‘fork and join’ flow control.