Skip to content

Conversation

@alexbozhenko
Copy link
Member

@alexbozhenko alexbozhenko commented Jul 23, 2025

@alexbozhenko alexbozhenko reopened this Jul 24, 2025
@alexbozhenko alexbozhenko requested a review from Jarema July 24, 2025 13:57
# Object Store

{% hint style="warning" %}
If your objects fit within the JetStream [maximum message size](/running-a-nats-service/configuration#limits) (default 1MB, not recommended above 8MB), you should use the [Key/Value Store](/nats-concepts/jetstream/key-value-store/) instead.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

definately use softer language - "consider using", for example.

{% hint style="warning" %}
If your objects fit within the JetStream [maximum message size](/running-a-nats-service/configuration#limits) (default 1MB, not recommended above 8MB), you should use the [Key/Value Store](/nats-concepts/jetstream/key-value-store/) instead.

KV store is inherently simpler and more reliable for smaller data, providing strong consistency and atomic operations without the complexity of chunking.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"more reliable" is quite ambigous. Same with "strong consistency" - One could argue about those.

I would simplify and just mention that for small values, consider using KV before switching to Object Store.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants