Since we're storing events in an intermediate collection and you consume them at your own rate, there is actually no need for this. They will just pile up until you can consume them
Well yeah for a simple queue where messages live in memory and disappear once consumed there are plenty of technologies that work (rabbitmq, redis...).
Here is the goal is not to just build a queue but rather have something persisted where you can inspect payload and replay even days after the original even was sent
yeah but in my experience it's either the information is very shallow (like status page) or too technical (like traces). i feel like non engineering parts of the org still want to have a view of what's slow, what's fast, how much data we ingested and things like that
Since we're storing events in an intermediate collection and you consume them at your own rate, there is actually no need for this. They will just pile up until you can consume them