I think some of your pain might be alleviated with the PVS Tech Preview that’s going on. It’s specifically PVS in Azure. I know that’s full Citrix Virtual Apps and Desktops Service (CVADS) vs CVADS Standard in Azure but it’s something to look into. And regarding the docs, have you checked the full docs site for CVADS Standard for Azure? https://docs.citrix.com/en-us/citrix-virtual-apps-desktops-standard-azure.html. Source: over 3 years ago

Unfortunately, the API we created is not suitable for anything but the most basic prototyping. For a real API, we will likely want to use our own domain. This appears to be quite complicated in GCP. We will need a Load Balancer, a serverless NEG and an API Gateway among some other components. See Getting started with HTTP(S) Load Balancing for API Gateway and HTTP(S) Load Balancing for API Gateway. - Source: dev.to / over 1 year ago

Set up a Load Balancer and Cloud Armor in front of your function, or. Source: over 1 year ago

In this article, I’ll show you how to configure a global cloud load balancer that serves as both a proxy and a load balancer. This type of load balancer comes with a single IP address that can be accessed from any location on earth and can route a request to the nearest (active!) application instance. - Source: dev.to / over 1 year ago

Cloud Load Balancing for distribution. - Source: dev.to / almost 2 years ago

While the precise features of the application are immaterial, the architecture is of primary importance. A lot of tools (and buzzwords) come to mind when trying to architect a modern web application. Assets can be served from a CDN to improve page load speed. A global load balancer can front all traffic, sending requests to the nearest server. Serverless functions and edge functions can be used to handle requests,... - Source: dev.to / almost 2 years ago