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.

Sign up for GitHub

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

Jump to bottom

consider having routing and server in a single process #67

Open
jhellerstein opened this issue Jul 5, 2018 · 0 comments
Open

consider having routing and server in a single process #67

jhellerstein opened this issue Jul 5, 2018 · 0 comments

Comments

@jhellerstein
Copy link
Collaborator

jhellerstein commented Jul 5, 2018 •
edited
Loading

these are ostensibly separated because there's much more serving traffic than routing traffic, and we can deploy many fewer routing nodes. Still, doesn't seem very harmful to have that lightly-used service embedded in the server process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jhellerstein