Removing dispatcher job #81
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is now going to be its own seperate service.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the dispatcher job, and silos it into its own service located here. With this change, the server service should be horizontally scalable and furthering the goal of separating different parts of the application into microservices has been achieved.
Also, this pull request adds the other end of the logic required to connect link operations back to their founding link. All this change is doing is reading data from redis that the first part of the migration, a
workerchange, added there. Here was the first part of the migration: backstrokeapp/worker#3With this change, here's what the new infrastructure diagram looks like (both
serverandworkerare horizontally scalable):