Architecting the solution

With all the information collected from each section of the HipLocal case study, we can proceed with proposing a solution.

Figure 13.1 – HipLocal proposed solution

Within the solution, we can observe the following elements:

• Cloud Load Balancer: Cloud Load Balancer will allow us to redirect user requests to the closest instances to their location in order to comply with the executive statement and business requirements that indicate that the user has to have the same experience no matter where they are (https://cloud.google.com/load-balancing).
• Compute Engine and managed instance groups: Compute Engine is where the application APIs are currently deployed. This allows us, together with the managed instance groups, to create new instances based on the user flow that we are receiving and thus comply with the technical requirement that indicates that the solution must scale depending on the user demand and the business...