I shared my experience in an abstract style.

1. I N C O G N I T O F A C T O R S
JUNE 10, 2019 CASE STUDY 2
The real time scenarios with abstracts
The world largest professional services organisation
had a frequent issue of an Enterprise application.
Even though the application was for internal users,
the features and the services were paramount for
their business. They wanted to bring it normal
operational mode with no hassle. Hence they decided
to identify the incognito factors and mitigate it as
soon as possible to run the business as usual.
How to identify the
application issues
and approaches for
providing valuable
solutions
by Sivakumar Kulandhaivel
CLUSTER: PROFESSIONAL
SERVICES FIRM
LOCATION: UK AND USA
AIM : ADDRESS THE
FREQUENT OUTAGE OF AN
ENTERPRISE APPLICATION
GLANCE OF CASE STUDY
OUTPUT VALUES:
1) PROVIDED A QUICK FIX TO CONTINUE
THE BUSINESS
2) INTRODUCED A NEW PROCESS TO
KNOW THE CURRENT STATE OF THE
APPLICATION
3) IDENTIFIED THE ROOT CAUSE OF THE
WRONG CODE AND DESIGN
4) AUTOMATED THE CONTINUOUS
DEPLOYMENT TO REDUCE THE
OPERATIONAL COST
5) PROPOSED TO IMPLEMENT CONTAINER
ARCHITECTURE

2. JUNE 2019 CASE STUDY 2
I gathered the high-level application
architecture and information about the issues,
history of the application, life cycle of the
system and its road map at the initial meeting
to brainstorm. Then I collected the following
details such as current production environment
of the application including hardware and
network, memory allocation, shared application
information, last 3 months of release
management information, application, database
and server log files and last 5 core dump files.P H O T O B Y K U M S H I V
My quick fix solution was providing a breathing
space for all key stakeholders. As per process, a
request was raised to empty the tmp folder in the OS
server and implemented a script to maintain
sufficient space automatically in it. Based on the
analysis, removed all the unwanted applications from
the shared server. It happened within a week of the
time, besides increased the client's confident.
Both the solutions presentation contained details of approaches and cost benefits along with
the implementation plan. As a result, both clients and all key stakeholders could take a quick
decision and at the end they were able to see the tangible business value.
Approaching Solutions
Tactical Solution
As I anticipated, my initial analysis gave me surprises. Firstly, the application was running in
an inadequate space in OS server. Secondly, it was deployed in a shared portal application
server. Finally, a myriad of out of memory and null pointer errors found from the log files.
Conclusion
Strategic Solution
The strategic solution given, after a careful analysis
of the application architecture, available log files
and results from profiling tool and load test. The
solutions were a) refactor the codes to address
memory leaks, db connections and inappropriate
designs, b) deploy the application server instead of
portal server - intrinsic services consumed memory, P H O T O B Y K U M S H I V
CPU and created expensive threads-, c) implement the separation of concerns by using
container architecture and d) designed an automation for continuous deployment.