Please review the previous lab on Splitting Traffic between Multiple Versions in App Engine before proceeding with this lab.<https://scribehow.com/shared/Splitting_Traffic_between_Multiple_versions_in_App_Engine__kwQ4SifqSDKbFywF9khubg>

Type "**App Engine"** in the search bar and click on the **App Engine** option

**What is an App Engine?**\
\
Google Cloud Platform's App Engine is a fully managed, serverless PaaS that enables developers to build and deploy scalable web applications with minimal infrastructure management. It offers automatic scaling, supports multiple programming languages, and provides two environments: Standard (for rapid scaling with standard runtimes) and Flexible (for custom runtimes and Docker containers). Integrated with GCP services and tools, App Engine ensures high availability, security, and cost-efficiency, making it ideal for web apps, mobile backends, and APIs. Developers can focus on code while GCP handles infrastructure, scaling, and maintenance.

**What are Versions in App Engine?**\
\
In Google Cloud Platform's App Engine, versions are different iterations of your app's deployment, allowing you to manage multiple versions within the same service for efficient updates and testing. Each deployment creates a new version, enabling traffic splitting for A/B testing or gradual feature rollouts, and facilitating quick rollbacks in case of issues. Versions scale independently based on traffic and can have distinct configurations, streamlining the development, testing, and deployment processes of your applications.

On the **Versions** wizard, here you can view the **Traffic Allocation**

To switch all the traffic to V2, checkbox the Version **v2** option

Click on the **MIGRATE TRAFFIC** button on the top left side to Migrate the traffic to V2

To View the Split traffic settings, click on the **SPLIT TRAFFIC** button on the top left side

**What is Split Traffic?**\
\
Split traffic in Google Cloud Platform's App Engine allows you to distribute incoming requests across different versions of your application. This feature enables A/B testing, gradual rollouts of new features, and performance comparisons by directing a specified percentage of traffic to each version. It helps in monitoring and assessing new versions without fully committing to them, ensuring a smoother transition and minimizing potential disruptions.

**Split traffic** wizard will open, here you can modify the **Split traffic by** option like IP addresses

**What is Split traffic by IP address?**\
\
Split traffic by IP address in Google Cloud Platform's App Engine allows you to route incoming requests to different versions of your application based on the client's IP address. This method ensures that all requests from a particular IP address are consistently directed to the same version, providing a stable experience for the user and facilitating more accurate A/B testing or phased rollouts. It helps maintain session consistency and improve the reliability of version comparisons.

Scroll to the **Traffic allocation** section here you can add more Versions for Traffic Allocation to do this click on the **ADD VERSION** button

Click on the **SAVE** button to save the modified changes

Congrats on exploring split traffic allocation configurations!

On the **Cloud Shell Editor** wizard, click on the **my-first-service** dropdown from the left bar

On the right side **app.yaml** code will be displayed

To deploy the **my-first-service**, on the **Cloud CLI**, first run [[cd..]] command to return to the previous directory, then run the command [[cd my-first-service]].

Google Cloud

This guide provides step-by-step instructions for creating a new service and using App Engine.

Create a New Service and Playing with App Engine