---
title: "Discussion on \"How to Migrate an Application from AWS to GKE [Full Book]\" | Hashnode"
description: "Discussion on \"How to Migrate an Application from AWS to GKE [Full Book]\". This guided lab walks you through migrating a small payments app, with a React UI and Express API running on a single AWS EC2 instance, while PostgreSQL stays on AWS.\nYou’ll move the UI and API to Goo"
url: "https://hashnode.com/posts/how-to-migrate-an-application-from-aws-to-gke-full-book/6ad245772c56514e6fd78db7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to Migrate an Application from AWS to GKE \[Full Book\]](https://freecodecamp.org/news/how-to-migrate-an-application-from-aws-to-gke-full-book?utm_source=hashnode&utm_medium=feed)

This guided lab walks you through migrating a small payments app, with a React UI and Express API running on a single AWS EC2 instance, while PostgreSQL stays on AWS. You’ll move the UI and API to Goo

Oct 16 · 156 min read · freecodecamp.org  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)
-   [#cloud-migration](https://hashnode.com/tag/cloud-migration)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#gke](https://hashnode.com/tag/gke)
-   [#aws](https://hashnode.com/tag/aws)
-   [#book](https://hashnode.com/tag/book)

## Written by

[Osomudeya Zudonu](https://hashnode.com/@Osomudeya)

@Osomudeya

  
[View profile](https://hashnode.com/@Osomudeya)

Devops and Cloud Engineer

DevOps and Cloud Engineer. I break down Kubernetes, multi- cloud infrastructure into hands-on guides for beginners, career switchers, and engineers leveling up.

## Responses 2

Markdown supported · ⌘↵ to post

[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%?

[StackShortlist](https://hashnode.com/@veristria)

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

Keeping PostgreSQL on AWS and shifting traffic a few percent at a time behind the same public URL is a realistic way to structure a migration, since it avoids moving the hardest piece on day one. Putting 'Prove a Retry Never Charges Twice' in Part 1, before any cloud work, is a nice touch for a payments app. Recording the AWS baseline before planning the move also gives the later load tests something concrete to compare against.