---
title: "Comment by Rahul R on \"How to Migrate an Application from AWS to GKE [Full Book]\" | Hashnode"
description: "During the gradual traffic shift from AWS to GKE, both environments share the same PostgreSQL database on AWS. How would you prevent database connection pool ex"
url: "https://hashnode.com/posts/how-to-migrate-an-application-from-aws-to-gke-full-book/6ad245772c56514e6fd78db7/comment/6ad322c3eb06abf774271f14"
---

[Discussion](https://hashnode.com/posts/how-to-migrate-an-application-from-aws-to-gke-full-book/6ad245772c56514e6fd78db7)

Comment [How to Migrate an Application from AWS to GKE \[Full Book\]](https://hashnode.com/posts/how-to-migrate-an-application-from-aws-to-gke-full-book/6ad245772c56514e6fd78db7)

[Rahul R](https://hashnode.com/@rahul-data)

[Oct 17](https://hashnode.com/posts/how-to-migrate-an-application-from-aws-to-gke-full-book/6ad245772c56514e6fd78db7/comment/6ad322c3eb06abf774271f14)

During the gradual traffic shift from AWS to GKE, both environments share the same PostgreSQL database on AWS. How would you prevent database connection pool exhaustion and cross-cloud latency from affecting payment transactions as GKE traffic increases from 1% to 100%?