-
Notifications
You must be signed in to change notification settings - Fork 207
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
Moving to GCP #157
base: master
Are you sure you want to change the base?
Moving to GCP #157
Conversation
* master: Remove comments Clean up
* master: Update readme and prettier Test and build
* 'master' of github.com:excalidraw/excalidraw-room: Add test images (#165)
* 'master' of github.com:excalidraw/excalidraw-room: const
@kbariotis The goal is to replace the heroku server, not to add another server on top. That said, while we can move to GCP temporarily to improve perf, we'll want to use a different host because the pricing of GCP App Engine is criminal (unless we put the instances to sleep if unused, but long-term (even short-term) that's not gonna be a solution because the traffic will be unyielding). But, mid-term we'll want to use several instances for sure. |
@dwelle sorry I should have link to the code. I meant this horizontal scaling. I'm personally not sure how the app will handle multiple instances. |
I have some updates about GCP.. it might be a bit cheaper than we think :) |
We are keep getting more and more errors from Heroku, so in general we are investigating to move away.
Rationale for moving to GCP
We are already using the following services from Google:
So instead of getting yet another service like DO or AWS, why not continuing adding to GCP, since we already have bunch of things there and one active billing account.
Pros
Cons
Either case we shouldn't reject something just because it's a bit more expensive, especially if it offers benefits and we should never care about the performance and downtimes.
To test this PR on GCP
Useful links