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 revamp focuses on the workflow of bridgre core. For example, the
processBatchLogs
flow orderly goes as below:controller
fetch logs from nodepool
pool
orchestrate jobs to workersworker
triggers the process behind thejob
and does further processjob
contacts directly tolistener
This flow shows no signature in each
component
. In fact, they are multiple layers sharing the same responsibility so features can be placed anywhere instead of in a specific layer.The revamp rearranges the flow
controller
fetch logs from nodeorchestrator
orchestrator
getsworker
frompool
then assignsjob
forworker
worker
contacts directly tolistener
and call the perspective callback based on job's informationThe new flow split
pool
into two components:orchestrator
andpool
.job
no longer does any logic, they convey data instead.Afterward, the flow is composed from these components:
controller
: fetch logs then feedjobs
orchestrator
: deliverjob
to properworker
frompool
pool
: collection of items prepared to use laterworker
: set of logic to process jobjob
: set of data required for a request