To fulfill their requirement, we recommend using AWS Amazon Location Service. By utilizing the Geocoding feature, we can easily get the name of the city, until the sub-district level. The MNC team created an aggregator application to make requests to the Amazon Location Service service. To get regional data, the aggregator application will receive a payload in the form of longlat. The region name will be queried to documentDB, which will later return the area code. The area code will be used by the calling service to display news that is appropriate to the reader's area.

Then, we propose to use ECR as the docker repository, Amazon EKS as the orchestrator. This will help them reduce the daily operations of managing their kubernetes cluster. Using the Amazon EKS service, the team focused on developing the application and deploying it.

We also recommend using the AWS Elasticache service to cache locations. The goal is to shorten the waiting time to get a location, so that the user experience becomes better. Then the accuracy of the longlat sent also varies from one device to another. With these variations, there are applications that send decimal precision of 5 to 8 digits. This makes the number of requests sent to the Location service massive, with the location data returned no different. To overcome this, we recommend rounding decimal data to 3 digits. The 3-digit accuracy on longlat has a precision distance of about 111m, so it is considered still in one area.

We create development and production accounts separately, and are managed within the MNC organization. We also separate the accounts for each environment following AWS best practice, to keep a secure environment on the development account, this will also help the development team to quickly generate resources making it agile.