[WIP] Populate each service's data separately #50
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.
Right now, billow updates can take hours (or days) because of the size and rate limiting on our account. If a single stage in a job fails, the entire update fails and prevents any data from syncing.
This PR refactors the system so that each AWS service's data updates in its own job, so EC2 queries failing won't impact RDS data collection. A full initial build is still required on startup so we don't end up with an incomplete view of the data, but afterwards the services will update incrementally
Reviewers
@jtai @erluoli