Are Jetstream push subscribers completely deprecated? #652
-
Coming from NATS Streaming, which only had push consumers, we originally migrated our consumers in Jetstream as push consumers as well. Now that we're doing some code cleanup, it seems that the original Jetstream Does it mean, that push subscribers are going to be completely removed from NATS at some point, in favor of pull subscribers, and they should be completely avoided? Or maybe I simply missed the proper API that should be used to create them? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The push subscriber will remain there, however you should not use it - the new consumers abstraction - https://github.com/nats-io/nats.deno/blob/main/jetstream.md#consuming-messages does exactly what you want, but it does it behind a pull consumer. In terms of your code, it will feel like a push, but will have all the benefits of a pull consumer. Use this instead please. |
Beta Was this translation helpful? Give feedback.
The push subscriber will remain there, however you should not use it - the new consumers abstraction - https://github.com/nats-io/nats.deno/blob/main/jetstream.md#consuming-messages does exactly what you want, but it does it behind a pull consumer. In terms of your code, it will feel like a push, but will have all the benefits of a pull consumer. Use this instead please.