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
We're excited to announce Encore v1.19.0 which brings a highly requested feature: support for message ordering in Pub/Sub!
Ordered topics ensure messages are delivered to subscribers in the order they were delivered (for messages that share the same ordering key). This can make it easier to implement certain use cases where message ordering is important.
Message ordering is not a free lunch and reduces message delivery throughput. To maintain topic order, messages with the same ordering key aren't delivered until the earliest message is processed or dead-lettered, potentially causing delays due to head-of-line blocking. For more information see the docs.
To create an ordered topic, define a message attribute to be used as the ordering attribute. For example:
Remember to first update to the latest version of Encore using encore version update, and update your dependency on encore.dev within your app so your IDE sees the new configuration option, using go get -u encore.dev@latest.
What’s next
We're working on adding more flexibility in controlling underlying infra for individual services, deploying to Kubernetes, and much more. We're also working on bringing a bunch of improvements to the local development dashboard.
Stay tuned and please vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack or post on the Community Forum.
We’re excited to hear your feedback, and happy Pub/Subbing! ❤️
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're excited to announce Encore v1.19.0 which brings a highly requested feature: support for message ordering in Pub/Sub!
Ordered topics ensure messages are delivered to subscribers in the order they were delivered (for messages that share the same ordering key). This can make it easier to implement certain use cases where message ordering is important.
Message ordering is not a free lunch and reduces message delivery throughput. To maintain topic order, messages with the same ordering key aren't delivered until the earliest message is processed or dead-lettered, potentially causing delays due to head-of-line blocking. For more information see the docs.
To create an ordered topic, define a message attribute to be used as the ordering attribute. For example:
Remember to first update to the latest version of Encore using
encore version update
, and update your dependency onencore.dev
within your app so your IDE sees the new configuration option, usinggo get -u encore.dev@latest
.What’s next
We're working on adding more flexibility in controlling underlying infra for individual services, deploying to Kubernetes, and much more. We're also working on bringing a bunch of improvements to the local development dashboard.
Stay tuned and please vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack or post on the Community Forum.
We’re excited to hear your feedback, and happy Pub/Subbing! ❤️
This discussion was created from the release Pub/Sub message ordering.
Beta Was this translation helpful? Give feedback.
All reactions