Replies: 3 comments 6 replies
-
The binary files put into the nats object Store are chunked by me. I do this so that it’s resilient when putting large ikes in and out. I have had success with 50 gb video files . By chunking the server memory does not increase. The destination of the files can be local or s3. Just thought this is useful to know in terms of use cases and technical resiliency |
Beta Was this translation helpful? Give feedback.
-
Hey @gedw99! We have two connectors because the Publish-Subscribe and JetStream implementations differ a lot and the configuration is quite different as well, so it didn't make that much sense to have a single connector. I see that you already opened a feature request for objects and key-values, thanks for that! |
Beta Was this translation helpful? Give feedback.
-
For reference the ticket which is about implementing this feature: conduitio-labs/conduit-connector-nats-pubsub#45. |
Beta Was this translation helpful? Give feedback.
-
Nats also supports objects ( files ) and kv ( key values ).
Not sure why there are 2 ?
https://github.com/conduitio-labs/conduit-connector-nats-pubsub
https://github.com/conduitio-labs/conduit-connector-nats-jetstream
It would be nice if this was supported too. From what I can it’s not ?
it should be possible because both support cdc semantics of created, updated and deleted.
I use nats for syncing files and kv values across systens. It’s a great way to manage server resources like binary’s that need to be in many places. Kv is a create way of updating configs across many servers.
Beta Was this translation helpful? Give feedback.
All reactions