+++
title = "Modernize"
chapter = false
weight = 60
+++
#### Alex is the Development Lead for the modernization project at AD Financial. He has been be working closely with Nathan to implement the modernized application, utilizing several AWS services. Alex understands how using modern cloud services, including container management technologies, can accelerate the performance, deployment, and management of mission critical applications.
#### During the Modernization phase, Nathan and his team derived the following conclusions based on their findings:
<span style="color: #4e3eb1;"><i class='fas fa-certificate fa-sm'></i></span> The frontend web components were not the primary cause of high end user response times related to the loan approval process.
<span style="color: #4e3eb1;"><i class='fas fa-certificate fa-sm'></i></span> Business loan processing and personal loan processing need to be separated into multiple independent services so they can be independently scaled and maintained.
<span style="color: #4e3eb1;"><i class='fas fa-certificate fa-sm'></i></span> The need to have a more scalable, long-term archive storage solution for the loan audit data.
<span style="color: #4e3eb1;"><i class='fas fa-certificate fa-sm'></i></span> The collocation of loan data and audit data was constraining the database and needed to be split into independent repositories.
<span style="color: #4e3eb1;"><i class='fas fa-certificate fa-sm'></i></span> The need to have monitoring intelligence down to the infrastructure layer for each component accessible within the same UI.
<br>
AWS offers multiple services for container orchestration and storage. After careful consideration, the decision was made by the team to move forward with the following AWS stack that would best meet their technical and business requirements derived during the Mobilization phase.
<span style="color: #4e3eb1;"><i class='fas fa-check-square'></i></span> **Container Orchestration Selection**
<span style="color: #efc100;"><i class='fas fa-certificate'></i></span> **AWS Elastic Kubernetes Service (EKS)**
<span style="color: #4e3eb1;"><i class='fas fa-check-square'></i></span> **Storage Solution Selection**
<span style="color: #efc100;"><i class='fas fa-certificate'></i></span> **AWS Simple Storage Service (S3)**
<span style="color: #4e3eb1;"><i class='fas fa-check-square'></i></span> **Database Solution Selection**
<span style="color: #efc100;"><i class='fas fa-certificate'></i></span> **AWS Relational Database Service (RDS)**
<br>
For container orchestration **EKS aligns well with the teams requirements**, having the ability **to automate scaling, managing, updating, and removing containers at will** without incurring any system downtime.
**S3 (Simple Storage Solution)** was chosen to host the audit data as it **provides an affordable and robust solution** to securely archive the needed audit trail while supporting high retrieval and ingestion rates with the ability to scale dynamically.
**AWS RDS was chosen** as the new database backend as it **provides the high availability and fault tolerance needed** with **real time replication across multiple availability zones and/or regions**.
<!--
{{% notice info %}}
**Optional:** You can explore the artifacts that were utilized to deploy the application and AppDynamics agents associated with this section by navigating to the following directories listed below that are located on your Cloud9 instance:
{{% /notice %}}
```
/home/ec2-user/environment/deployment
/home/ec2-user/environment/deployment/post-mod-kube-cluster
/home/ec2-user/environment/deployment/post-mod-kube-app
/home/ec2-user/environment/deployment/post-mod-kube-ma
```
-->
## Next <i class='fas fa-cog fa-spin'></i>
Now it's time to **create the EKS cluster**, deploy the application to the cluster, and look at how the AppDynamics agents are configured and deployed along with the application.