Your company runs one batch process in an on-premises server that takes around 30 hours to complete. The task runs monthly, can be performed offline, and must be restarted if interrupted. You want to migrate this workload to the cloud while minimizing cost. What should you do?
HTTP(S) load balancing is a Google-recommended practice for distributing web traffic across multiple regions and zones, and providing high availability, scalability, and security for web applications. It supports both IPv4 and IPv6 addresses, and can handle SSL/TLS termination and encryption. It also integrates with Cloud CDN, Cloud Armor, and Cloud Identity-Aware Proxy for enhanced performance and protection. A MIG can be used as a backend service for HTTP(S) load balancing, and can automatically scale and heal the VM instances that host the web application.
To configure DNS for HTTP(S) load balancing, you need to create an A record in your DNS public zone with the load balancer's IP address. This will map your domain name to the load balancer's IP address, and allow users to access your web application using the domain name. A CNAME record is not recommended, as it can cause latency and DNS resolution issues. A private zone is not suitable, as it is only visible within your VPC network, and not to the public internet.
HTTP(S) Load Balancing documentation
Felix
8 months agoJerry
8 months agoJoanna
8 months agoTimothy
8 months agoCarlton
8 months agoLisandra
9 months agoShasta
9 months agoNoah
9 months agoFrederica
9 months agoGwenn
9 months agoVerdell
9 months agoAlline
9 months agoAntonette
9 months agoGaynell
9 months agoGregg
1 year agoAnnamae
1 year agoCarylon
1 year agoDeeanna
1 year agoHarrison
1 year agoEura
1 year agoSerina
1 year agoTricia
1 year agoLeslie
1 year agoKayleigh
1 year agoJess
1 year agoJade
1 year agoRikki
1 year agoKaran
1 year agoMira
1 year agoVeta
1 year agoAdelina
1 year agoYong
1 year agoKimbery
1 year agoEarleen
1 year agoCandida
1 year agoPilar
1 year agoKarma
1 year ago