Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deploy to google app engine flex (GAE flex) #14

Open
maxheld83 opened this issue Jul 21, 2020 · 0 comments
Open

deploy to google app engine flex (GAE flex) #14

maxheld83 opened this issue Jul 21, 2020 · 0 comments

Comments

@maxheld83
Copy link
Owner

I think GAE flex in some ways suits us better; it seems more mature, better documented and "cleaner" than Azure Web Apps for containers.

However, the pricing structure is a big, big disadvantage for typical shiny loads as explained in subugoe/shinycaas#11.
As of now, GAE flex will open a new VM for every version of every service, which gets very expensive fast and also just wastes a lot of empty cycles.

By contrast, in Azure Web Apps for Containers, we can run several apps and even their slots (~versions) in the same VM, which suits our loads much better.

Weirdly, this is actually kind of an inconsistent design in Azure, because a (micro)services architecture would imply that each of the services can be scaled independently, and sharing a VM kind of defeats that purpose.
But good for us, for now.

In the long run, a cleaner design such as GAE flex might be preferable, if:

  • GAE flex allows <1 vCPU/Instance (RAM would still make it expensive)
  • GAE flex allows us to share VMs (making it like Azure Web apps)
  • GAE flex scales to 0 and/or Google Cloud Run allows websockets and/or miraculously allows stateful apps (not happening) subugoe/shinycaas#13

Anyway, keeping this open, might check back in a year or so.

Related: subugoe/hoad#25

@maxheld83 maxheld83 transferred this issue from maxheld83/muggle Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant