-
Choosing a deployment platform
A high-level overview of how you could decide on the most suitable platform for your application.
-
Canary releases
A canary release is used when you create a new version but you want to only give it a small percentage of requests to test it for bugs before migrating 100% of requests to it. For example, give a new version 10% ot the requests and split the traffic randomly. You can then monitor for…
-
Blue Green Deployments
It’s basically a technique for releasing your application in a predictable manner with an goal of reducing any downtime associated with a release. It’s a quick way to prime your app before releasing, and also quickly roll back if you find issues.
-
A/B testing
A/B testing is used when you want to compare multiple versions of an app to seewhich is better. You can, for example, give two versions 50% of the traffic. Split by IP address, that way once a user starts getting one version they get that version for every subsequent request. You can then define some…
-
Deploying to Kubernetes
The gcloud container command group lets you create and manage Google Kubernetes Engine containers and clusters. Create cluster Connect and apply yaml file: Show the running pods: Show all the deployments:
-
Dockerfile
The Dockerfile is a recipe for how to build the container image, while .dockerignore defines the set of files that should be ignored when copying files into the image. Multistage Dockerfile:
-
Cloud Run traffic splitting
Split traffic across two or more revision:
-
HTTP(S) Load Balancing
Google Cloud’s HTTP(S) load balancing provides global load balancing for HTTP(S) requests destined for your instances. This means that your applications are available to your customers at a single anycast IP address, which simplifies your DNS setup. HTTP(S) load balancing balances HTTP and HTTPS traffic across multiple backend instances and across multiple regions. HTTP requests…