feat(log): sending audit log concurrently #140
Merged
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.
Summary
Sending notifications should be not be part of sync call as part of create appeal or update approval. For both these steps, audit log and sending notifications need not be part of synchronous call one by one since that would increase the entire time of the appeal flow. These two can be run concurrently.
Please refer to the issue #84 for the discussion.
Approach
Making the call async for audit log by applying go concurrency when sending the message through audit logger