🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Message ID shown in UI incremental, Is there a limit on this or it gets refreshed?

nomassama
nomassama Member Posts: 11 ✭✭
in PubSub+ Event Broker #1
image.png

Hi fellow Devs. I have distributed messages broker systems like nats and kafka etc. and I am new to Solace and first time getting myself to use UI.

I cant help but notice this. I saw this Message ID field is being maintained by either EventBroker or UI. In my recent run I sent 8 messages and read 8 messages would this be just like that and never reset ?
It Incremental till I have been doing my POCs. does it get reset at some point ? because when there are millions of transactions are being done this value will increase and may add extra overhead.


P.S I am coming from very raw low level development background so If I am going too deep into this I excuse 😅

Answers

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    edited August 28 #2

    Hi @nomassama , welcome to the Community! 🎉

    Thanks for checking out Solace, comparing to NATS and Kafka. Solace has some pretty cool features and functionality (and stability) over them.

    Anyhow… that ID that you're seeing in the PubSub+ Manager GUI is an internal Message Spool ID that's assigned by the broker when it stores a message in its message spool (i.e. to disk). It's not a number/identifier you as a client application can really do anything with… it's assigned by the broker automatically, and not readily available to consumer applications. And if publishing to lots of destinations, then the IDs on a single queue would not be sequential as the incoming messages would be spread across different queues.

    It is an 8-byte long, so would take a couple million years at 100,000 msg/s through the broker to roll over.

    An 8-byte ID is really not a lot of overhead! And there are a LOT of other IDs, metadata, headers, etc. associated with messages, connected applications, active flows, etc. that the broker keeps track of. I wouldn't worry too much about it.

Categories

This Month's Leaders

This Week's Leaders