I will. I still consider this as a fairly beginner firendly video. I will enter also more complex topics. But it seems obvious to me that I should cover the basics first.
In what cases does it make sense to use update? So far, I have always created a new message in another queue when the processing entered a different state. I have always found this to be a cleaner solution.
I have actually used in a few times. Update is useful when you have multi-step processes. You can place a message on a queue, then based on a status property or flag a first service takes it, performs some steps and then updates the status. Then a next consumer reads the property, sees that it has been updated on a certain status, does some processing and then updates the status again. Then the next service does the same. When you reach the last step of the workflow, the consumer takes it and since it is the last consumer to perform a step within the workflow, it dequeues it.
Thanks for the video. Love your azure content. Please upload more detailed videos on azure like this one. Thanks again
I will. I still consider this as a fairly beginner firendly video. I will enter also more complex topics. But it seems obvious to me that I should cover the basics first.
@@Codewrinkles yea sure, btw love your content.
Thank you for this video! Could you please make a tutorial about CosmosDB?
There will be plenty of tutorial on CosmosDB in the near future. Make sure to be subscribed and also turn on notifications.
In what cases does it make sense to use update? So far, I have always created a new message in another queue when the processing entered a different state. I have always found this to be a cleaner solution.
I have actually used in a few times. Update is useful when you have multi-step processes. You can place a message on a queue, then based on a status property or flag a first service takes it, performs some steps and then updates the status. Then a next consumer reads the property, sees that it has been updated on a certain status, does some processing and then updates the status again. Then the next service does the same. When you reach the last step of the workflow, the consumer takes it and since it is the last consumer to perform a step within the workflow, it dequeues it.
love it
I'm glad. Thank you.
Thank you for detailed explains
Glad you enjoyed it!