You have an application deployed in production. When a new version is deployed, some issues don't arise until the application receives traffic from users in production. You want to reduce both the impact and the number of users affected. Which deployment strategy should you use?

The organization you are working for manages an ecommerce site, and the application is deployed behind a global HTTP(S) load balancer. You are required to test a new product recommendation algorithm, and to determine the new algorithm's effect on sales in a randomized way, you plan to use A/B testing.

What is the recommended way to conduct testing for this feature?

Azgomi is a popular community application that facilitates communication between people in close proximity. It is used for event planning, organizing sporting events, and connecting businesses with their local communities. Although it launched recently in a few neighborhoods in Dallas, it is rapidly expanding into a global phenomenon. The company's venture capital investors are looking for rapid growth and expansion into new regions, offering the same experience to users, regardless of their location.

Azgomi wants to expand its service to new regions, with updated functionality to better serve its global customers. They plan to hire and train a new team to support these regions in their respective time zones. It is essential that the application scales smoothly and provides clear uptime data, and that they analyze and respond to any issues that occur. The existing technical environment is a mix of on-premises hardware and infrastructure running in Google Cloud Platform. The application runs on Compute Engine virtual machine instances hosted in GCP. State is stored in a single instance MySQL database in GCP. Release cycles include development freezes to allow for QA testing. 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 its footprint and support the increase in demand they are seeing. They require the following:

• Expand 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.

• Adopt Google-recommended practices for cloud computing.

○ Develop standardized workflows and processes around application lifecycle management.

○ Define service level indicators (SLIs) and service level objectives (SLOs).

The technical requirements for Azgomi include:

• Providing secure communications between the on-premises data center and cloud-hosted applications and infrastructure.

• The application must provide usage metrics and monitoring.

• APIs require authentication and authorization.

• Implement faster and more accurate validation of new features.

• Logging and performance metrics must provide actionable information to be able to provide debugging information and alerts.

• Must scale to meet user demand.

What steps can Azgomi take to revamp their architecture in order to accommodate a significant surge in user traffic?

The task at hand involves managing a sizable Google Kubernetes Engine (GKE) cluster. The current setup sees several application teams sharing a namespace to develop microservices for the cluster. The organization intends to bring on board additional teams for creating microservices. The aim is to set up multiple environments that guarantee optimal performance and security of each team's work. Furthermore, the objective is to minimize expenses while adhering to Google's best practices.

What actions do you need to take?

The ecommerce application under your management handles purchase orders from customers that are subject to cancellation or modification. You have observed that there is a high degree of variability in order volumes, and the order-processing system at the backend can only handle one request at a time. Your aim is to guarantee that customers are provided with seamless performance, irrespective of usage volume. It is imperative that customers' order update requests are executed in the order in which they were received.

What actions do you need to take?