Marking a series of service bus messages as START and END of a sequence
See original GitHub issueQuery/Question Problem Statement: I am publishing a series of messages to a service bus topic. Let’s say I have messages 1 to 100. They are all different messages in themselves but they are part of a series. I know we can set that series by using sessions(same session id for all those messages). But is there a way to say that message 1 is the start of that series and 100 is End of that series. Adding custom sequence numbers will allow me to achieve the same behavior but is there something which service bus provides to achieve that kind of sequencing?
Environment:
- Name and version of the Library package used: Microsoft.Azure.ServiceBus 4.1.1
- Hosting platform or OS and .NET runtime version (
dotnet --info
output for .NET Core projects): Azure AppService - .Net Core 3.1 - IDE and version: Visual Studio 16.5.4
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Azure Service Bus message sequencing and timestamps
This article explains how to preserve sequencing and ordering (with timestamps) of Azure Service Bus messages.
Read more >Implementing Multi Session Sequential Convoy Pattern ...
Using Azure Service Bus sessions, you can group related messages so that the message consumer locks a session and processes messages in the ......
Read more >Azure function with Servicebus how to not mark message ...
I have an Azure function that listens to messages in an Azure Servicebus queue. When it receives the messages it marks them as...
Read more >Azure Service Bus - Henrique Siebert Domareski
Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics (in a namespace — a ...
Read more >Troubleshooting Service Bus issues
Logging is performed for each operation and follows the pattern of marking the starting point of the operation, it's completion, and any exceptions...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Sandeep321, if you require all 10 messages to be received prior to taking any action and the last message should be a marker message, sessions are what you need. When you receive messages in a session, you can have a session state which could store the information from the previous 9 messages until the last, 10th, is processed.
Look at subscriptions. Receive operations with sessions are only possible on the entities that can be used to receive messages (queues and subscriptions).