task (3): Integrating the S3 upload logic with the GraphQL resolver #2
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.
S3 Engine offloads the audio upload task from the GraphQL resolver.
The idea being, the client should never be held up for any upload or processing tasks.
Ideally, the mobile client will upload the asset/audio directly to S3 using a signed URL, saving us network bandwidth, CPU time and a better overall experience for the user.
Sample mutation for uploading an audio short:
Altair client UI screenshot: