For online banking, stability of the system is the top priority. In the commonly expressed values using the APM tools,
we reach about 2,000 TPS, and as for concurrent logins, our system has a relatively high capacity to accommodate up to 22,000 users.
Transaction Path in MaxGauge is like seeing a very concise diagram in the midst of a very complex system. For instance, it displays the overall flow of a user ‘A’ logging in and accessing which server and moving about in which manner and etc., at a glance. This overall flow helps to understand and delegate the task in real world, and even it is used as communicating method among the administrators. Therefore, the transaction path is the greatest weapon for MaxGauge.
Since we have adopted MaxGauge into our system, we have never had not even one situation where we failed to recognize potential issues, giving way to bigger problems or extended system downtime.
When it is said, “A transaction is currently hung somewhere,” for systems of 1 Tier or 2 Tier, ‘where’ the transaction is hung may not be a critical. However for systems with 3 or more Tiers involving many connections and complicated business systems, the ability to quickly identify where the problem occurs is very critical.This ability is also very closely associated with finding the root cause of the problem and hence, sooner we can identify the cause, more quickly we can resolve the issues. My conclusion is that in the event of system failure, you can quickly analyze and resolve the issues because MaxGauge pinpoints the problem with specific data. But the best thing about MaxGauge is that you can prevent problems before they turn into critical issues.
MaxGauge is a one of a kind tool to actually materialize an integrated monitoring system by connecting each transaction in a complex N-Tier structure including the DB and Application Server.
When you are monitoring with MaxGauge, the DBA and Application Server administrator are viewing the same data. There is no room for argument. For example, everyone looks at the same data from the same point of view as to evaluate whether it is a DB problem or a Application Server problem and hence, everyone can come to a clear conclusion.
It is not easy to integrate DB and Application Server into a total transaction monitoring. I believe there were many attempts made even in the past; however we are the first, at least in the financial market, to actually implement and bring it to reality into a screen.
Let’s suppose there’s a problem. When there is a delay in transactions, I can simply look at the monitoring screen without taking any other actions to instantly identify where the process got into trouble. One of the best advantages in monitoring is that you are not so buys as before. The IT job which used to be constantly under time constraint and pressure has now become more simple and convenient. If you use MaxGauge, you will immediately notice the difference in your work. What more could we ask for, working in IT? Besides, if a tool can guarantee accurate and reliable data, everyone must use the tool.
For any one working in other companies or in financial services, if you feel that your system is too complicated, I strongly recommend that you use this type of end-to-end solution.
If you continue to use the old method in which each system is using its own specialized analysis method, then you will just end up wasting a lot of time. In financial services, time has a direct effect on monetary losses and so in that sense, I highly recommend you to try MaxGauge. Once you try it, you will know exactly what I’m saying!
