Clients about jetstream

[ripienaar]

There might be others but I saw https://github.com/c16a/nats-dart, JetStream doesnt need any special clients so you could use an existing core nats one like that.

There might be others, @ColinSullivan1 might know?

[winwisely99]

thanks @ripienaar

thanks for the link to that dart code. As far as i can see its very incomplete. This is always going to be the issue for Clients for NATS / JetStream too.

The other option i have is to embed the golang client inside Flutter.
Then we are not reliant on Dart client for NATS.

Good example on the cocept is here: https://github.com/deromask/deromask

• this works fully on Desktop and Mobile by using gomobile and embedding this.
• Protobufs are used between gomobile and Flutter layers.

Would appreciate and thoughts on this also...

[ripienaar]

If you can embed go stuff in flutter then that sounds like a winner :)

[winwisely99]

Cheers. Will give it a go and let you know how we get on.

Thanks for your advice

[ripienaar]

Closing this one, feel free to open another issue if you have more questions :)

[winwisely99]

@ripienaar

https://github.com/c16a/nats-dart is very old and incomplete

https://github.com/chartchuo/dart-nats looks to be getting close to feature complete.

We might help. Nit sure yet though as we are reviewing options.

[ColinSullivan1]

Help would be greatly appreciated, and we'd welcome another contribution in this area. I'm not aware of any other dart client beyond the ones mentioned above.

[winwisely99]

@ColinSullivan1

We have isolated 3 approaches:

1. Get on board and help the dart NATS client
2. Embed the NATS go client via go-mobile
   3 wrap the NATS server with GRPC

Option 3 looks like the most interoperable.
We need an untyped interoperability solution because our funders and users are orgs using a variety of languages. By wrapping NATS server side it will allow their microserices to easily talk to the gateway as well as the flutter client to talk to the gateway.

I wonder if Jetstream will be moving to a grpc based API ?

[ColinSullivan1]

I'd think choices 1 or 2 would be ideal.

gRPC does have a lot of language bindings, but you lose location transparency, failover functionality, and NATS does have true multi-tenancy that can help you manage the orgs connecting to you. NATS does a multitude of client types... https://nats.io/download/#nats

JetStream won't have a gRPC interface; it'll use core NATS.