You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current handling of tweets is not thread-safe. In cases of high loads, there is a case where we may experience a sentiment score being incorrectly associated with a tweet.
Solution
A solution would be to encapsulate the logic for calling a cognitive service and the eventhub in a dedicated Azure Function (maybe a Durable Function?). Hence the Azure WebJob will solely focus on streaming data
Another solution would be to add an Azure Storage Queue that recieves input for each new event, with worker role picking up messages from the queue and sending them to the Azure EventHub
The text was updated successfully, but these errors were encountered:
Originally from https://github.com/excellaco/azure-sentiment-analysis/issues/1
Issue
The current handling of tweets is not thread-safe. In cases of high loads, there is a case where we may experience a sentiment score being incorrectly associated with a tweet.
Solution
A solution would be to encapsulate the logic for calling a cognitive service and the eventhub in a dedicated Azure Function (maybe a Durable Function?). Hence the Azure WebJob will solely focus on streaming data
Another solution would be to add an Azure Storage Queue that recieves input for each new event, with worker role picking up messages from the queue and sending them to the Azure EventHub
The text was updated successfully, but these errors were encountered: