Book Image

Google Cloud Platform for Developers

By : Ted Hunter, Steven Porter
Book Image

Google Cloud Platform for Developers

By: Ted Hunter, Steven Porter

Overview of this book

Google Cloud Platform (GCP) provides autoscaling compute power and distributed in-memory cache, task queues, and datastores to write, build, and deploy Cloud-hosted applications. With Google Cloud Platform for Developers, you will be able to develop and deploy scalable applications from scratch and make them globally available in almost any language. This book will guide you in designing, deploying, and managing applications running on Google Cloud. You’ll start with App Engine and move on to work with Container Engine, compute engine, and cloud functions. You’ll learn how to integrate your new applications with the various data solutions on GCP, including Cloud SQL, Bigtable, and Cloud Storage. This book will teach you how to streamline your workflow with tools such as Source Repositories, Container Builder, and StackDriver. Along the way, you’ll see how to deploy and debug services with IntelliJ, implement continuous delivery pipelines, and configure robust monitoring and alerting for your production systems. By the end of this book, you’ll be well-versed with all the development tools of Google Cloud Platform, and you’ll develop, deploy, and manage highly scalable and reliable applications.
Table of Contents (17 chapters)

Migrating databases to Cloud SQL

While greenfield applications are easy to get started on with Cloud SQL, many teams will want to capitalize on the managed MySQL and PostgreSQL experience for existing databases hosted outside of Google Cloud. With first generation MySQL instances, it was possible to configure external masters. This provided a clear migration path as the new instance could simply replicate all data from the external master until eventually moving clients over to the new instance.

With second generation instances, external masters are currently not supported. Migration to a second generation MySQL instance will unfortunately require some level of downtime, as writes must be disabled for the original MySQL instance and data must be imported into the new instance. The total downtime can be drastically reduced by migrating historical data before disabling writes on...