Skip to content

Add banner to object store doc #850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alexbozhenko wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add banner to object store doc #850

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
17d19e6
upd doc
alexbozhenko Jul 23, 2025
870d0e1
nit
alexbozhenko Jul 23, 2025
ab488a6
nit
alexbozhenko Jul 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions nats-concepts/jetstream/object-store/obj_store.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# 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

@Jarema Jarema Jul 25, 2025

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.


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

@Jarema Jarema Jul 25, 2025

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.

{% endhint %}

JetStream, the persistence layer of NATS, not only allows for the higher qualities of service and features associated with 'streaming', but it also enables some functionalities not found in messaging systems.

One such feature is the Object store functionality, which allows client applications to create `buckets` (corresponding to streams) that can store a set of files. Files are stored and transmitted in chunks, allowing files of arbitrary size to be transferred safely over the NATS infrastructure.
Expand Down