feat: use data from MinIO hosted s3 buckets #289
Draft
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
hairmare
force-pushed
the
feat/use-local-s3-buckets
branch
from
731264b
to
9243578
Compare
hairmare
force-pushed
the
feat/use-local-s3-buckets
branch
from
9243578
to
0acb343
Compare
11 tasks
|
The fact that this change would make it harder for others to re-use this is one of the main reasons this is currently not being pursued further. Adding some modularity would let us keep both if this is further explored. |
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.
By storing a copy of the ACRCloud data on our own systems we cut down on API usage and the monthly report can be generated fully in-house.
The referenced S3 buckets are world-readable, but only reachable from the RaBe network.
The code that fills these buckets it all over the place, acr-loader loads data into the
acrcloud.rawbucket daily on a cron, acr-ingest notices this and creates versioned entries inacrcloud.music. They "talk" to each other via some Kafka topics full of S3 events from MinIO that are consumed as CloudEvents thanks to the minio-cloudevents-service. It's pretty much a bog standard event processing pipeline following a (cloud-native-ish) microservice architecture.