This is a dedicated watch page for a single video.
Azgomi is a community application that facilitates communication between people in close proximity. It is used for event planning, organizing sporting events, and for businesses to connect with local communities. It recently launched in a few neighborhoods in Dallas and is rapidly growing into a global phenomenon. Azgomi's unique style of hyper-local community communication and business outreach is in demand worldwide. The company's venture capital investors want to see rapid growth and the same great experience for new local and virtual communities that come online, whether their members are 10 or 10000 miles away from each other. They want to expand their existing service, with updated functionality, in new regions to better serve their global customers. They will need to ensure that the application scales smoothly and provides clear uptime data. Azgomi's environment is a mix of on-premises hardware and infrastructure running in Google Cloud Platform. The application's existing technical environment includes Compute Engine virtual machine instances hosted in GCP, a single instance MySQL database in GCP to store state, exporting data to an on-premises Teradata/Vertica data warehouse, performing data analytics in an on-premises Hadoop environment, and no logging. Basic indicators of uptime are in place, and alerts are frequently fired when the APIs are unresponsive. Azgomi's investors want to expand their footprint and support the increase in demand they are seeing. Their requirements are to expand availability of the application to new regions, increase the number of concurrent users that can be supported, ensure a consistent experience for users when they travel to different regions, obtain user activity metrics to better understand how to monetize their product, ensure compliance with regulations in the new regions (for example, GDPR), reduce infrastructure management time and cost, and adopt the Google-recommended practices for cloud computing. Technical requirements include providing usage metrics and monitoring for the application and backend, requiring strong authentication and authorization for APIs, increasing logging, storing data in a cloud analytics platform, moving to serverless architecture to facilitate elastic scaling, and providing authorized access to internal apps in a secure manner. Azgomi wants to improve the resilience of their MySQL deployment while meeting their business and technical requirements. What is the recommended configuration for them to select?