Best practices for bringing your code to Google Cloud

While no migration to the cloud is exempt from risks, anticipating what could go wrong can help us have countermeasures ready to be implemented, thus reducing the negative effects, and that’s the main reason why we went through the list of common pitfalls.

But another way of making our migration less troublesome is to follow best practices that will also help us mitigate those risks, but this time by following specific actions and guidelines.

Either if we are designing a cloud-native application or if we are modernizing a legacy one to bring it to Google Cloud, we should keep in mind the following list of recommendations.

Avoid migrate and delete

I already mentioned this at some point in the book, and this is a common mistake that repeats again and again. Services are often migrated to the cloud just to have them decommissioned a few weeks later. This is an absolute waste of time and can have a negative effect...