I have an AppEngine Standard project that's been running for several years. Now I'm starting to have issues with some of AppEngine's limitations, such as no support for websockets.
I've started experimenting with Cloud Run and so far it's going well. I've created a service from the same codebase which works fine from the *.run.app URL and, using the "Domain Mappings" feature it also works on a burner domain.
The thing is, Domain Mappings is really limited and can't substitute for dispatch.yaml.
I have 3 domains (and a bunch of subdomains) that I route to various services. These routes need to change from time to time with no downtime. With dispatch.yaml I can do that easily - edit, deploy, done. Every change to Domain Mappings is a major event requiring 15 minutes to 24 hours downtime, so not an option.
It looks like Cloud Load Balancing would be a better way to go and I'd like to do some experiments but I have questions first!
- Is there a some other feature that would fit my needs that is less complex and doesn't cost money (dispatch.yaml is free after all)?
- If I create an experimental load balancer specifically for one domain and one cloud run service will it affect my production AppEngine services in any way? It looks like it should be OK but I don't want to risk everything going offline because I missed some configuration step. (In other words, I'm scared and I need someone to tell me I'll be OK!)
Thanks for any alternatives/advice/reassurance
