BatchPublisher with nats java

[suikast42]

I see the new relese notes of nats server 2.12.0. I want to try out the nats BatchPublisher with java client.

The stream config adds the option .allowAtomicPublish()

But I have see noting about batch publish options in nats java client. Instaed there is an extension library named orbit. https://github.com/synadia-io/orbit.java?tab=readme-ov-file. Here I see the Batch publishing. Do I need an extra library for that or will that optrion will be migrated in nats java client ?

[scottf]

As of now, there are no plans to combine orbit functions directly into the client library. This will allow us to more easily modify and release the extension without needing to release the client library, and also allows only those developers who want it to include it.

[suikast42]

As of now, there are no plans to combine orbit functions directly into the client library. This will allow us to more easily modify and release the extension without needing to release the client library, and also allows only those developers who want it to include it.

I can understand that approach. But the batch publish is a new jetstream capability and imho the batch publlisher should not an extension instead a core library function. Am I wrong ?

[scottf]

Especially since this is brand new, it will be easier to improve it without worrying about it being tied to a client library release. There is no technical need for this to be embedded in the client itself, in fact I would think it would be more appealing as an optional component that people don't have to carry in their distribution if they don't need it. For that matter, JetStream should be it's own component too and then KV.
If there ever is a new version, they will be separate components. As an example, consider our JavaScript library, which is split this way, only about 30% of users actually use JetStream. For them having smaller components is much more important.

[suikast42]

I have a different point of view on that, but of course it’s up to you. At the very least, a hint in the documentation would be very helpful. Otherwise, when reading about a new functionality in the release notes or documentation, you end up wondering how it can be solved using the standard library.