This is a dedicated watch page for a single video.
Azgomi is a community application designed for communication between people in close proximity, including event planning, organizing sporting events, and connecting businesses with local communities. The app is rapidly growing globally due to its unique style of hyper-local community communication and business outreach. The company wants to expand its existing services with updated functionality in new regions to better serve its global customers. They plan to hire and train a new team to support these regions in their time zones. Their 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 10,000 miles away from each other. To achieve this, Azgomi needs to ensure the application scales smoothly and provides clear uptime data, and that they analyze and respond to any issues that occur. Azgomi's existing technical environment is a mix of on-premises hardware and infrastructure running in Google Cloud Platform. Their APIs run on Compute Engine virtual machine instances hosted in GCP, and state is stored in a single instance MySQL database in GCP. Release cycles include development freezes to allow for QA testing, and the application has no logging. Applications are manually deployed by infrastructure engineers during periods of slow traffic on weekday evenings. There are basic indicators of uptime, and alerts are frequently fired when the APIs are unresponsive. Azgomi's investors want to expand the availability of the application to new regions, support 10x as many concurrent users, 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. They also need to provide secure communications between the on-premises data center and cloud-hosted applications and infrastructure, usage metrics and monitoring, APIs requiring authentication and authorization, faster and more accurate validation of new features, and logging and performance metrics that provide actionable information to be able to provide debugging information and alerts. The application must scale to meet user demand. In this context, Azgomi wants to reduce the latency of their services for users in global locations. They have created read replicas of their database in locations where their users reside and configured their service to read traffic using those replicas. What is the most efficient way to decrease latency for all database interactions with minimal effort?