Without this effort, I'd have no access to information about news inside NATS. More people in open source should strive to dissolve their internal knowledge silos. I can proudly present you as the people that did this right.
The ability to create an exclusive subscriber is a very useful feature. Right now we are designing the architecture of the primary and backup subscribers and switching from backup to primary.
Thank you for a very informative conversation. Do I understand correctly that it makes no sense to use push-based subscriptions, since the consumer is always inside pull-based?
With the new JetStream client API, there is no longer an option to create push-based consumers. The previous API is still supported (and therefore existing push consumers), but using the new API going forward will use the pull-based model.
![ว้าว!ลุงบีมแบกทองมารับขวัญหลานกันยกบ้าน [cc] แดนแพทตี้ SS2 | EP.49 |](http://i.ytimg.com/vi/Osihq1OAs-4/mqdefault.jpg)
Without this effort, I'd have no access to information about news inside NATS. More people in open source should strive to dissolve their internal knowledge silos. I can proudly present you as the people that did this right.
The ability to create an exclusive subscriber is a very useful feature. Right now we are designing the architecture of the primary and backup subscribers and switching from backup to primary.
Nice! Are you doing this with the KV lock pattern described in the episode or some other means?
Thank you for a very informative conversation.
Do I understand correctly that it makes no sense to use push-based subscriptions, since the consumer is always inside
pull-based?
With the new JetStream client API, there is no longer an option to create push-based consumers. The previous API is still supported (and therefore existing push consumers), but using the new API going forward will use the pull-based model.
Meant radon.. not argon :facepalm:
Yeah was thinking as well, have the same RadonEye BLE box in the basement