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

Host each task as a separate Google App Engine service #94

Closed
mmilenkoski opened this issue Jun 23, 2021 · 1 comment
Closed

Host each task as a separate Google App Engine service #94

mmilenkoski opened this issue Jun 23, 2021 · 1 comment
Assignees
Milestone

Comments

@mmilenkoski
Copy link
Collaborator

Now that we use Google App Engine (GAE) to host our app, we can no longer use different ports for different tasks since we access the server through a domain. Instead, we can host each task as a separate service within our app. In this way, each task can have its separate domain. The potential benefit is that we do not have to interrupt existing tasks to add a new task. I haven't tried this yet. Let me know what you think and whether you have any alternative ideas.

Ping: @martinjaggi, @tvogels

GAE Reference:
https://cloud.google.com/appengine/docs/standard/nodejs/an-overview-of-app-engine

@mmilenkoski mmilenkoski self-assigned this Jun 23, 2021
@s314cy
Copy link
Contributor

s314cy commented Jun 23, 2021

I think a reverse proxy would be doing just fine. This is easily feasible with the 'http-proxy' library (https://github.com/http-party/node-http-proxy). This would allow the server to redirect incoming URLs to internal services running on various ports. The ports would be invisible to the client/user. Adding a new task would require to edit & restart the proxy only.

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

4 participants