Maximum known-good value for MaxMsgs in a JetStream stream

[asymmetric]

Hi,

I'm exploring using NATS JetStream to store data that should ~never be discarded, so that it can be picked up and replayed from the beginning by any new consumer.

The data is very small (~100B), so the metadata overhead would be quite large, but given its tiny size I was considering running a stream without a MaxMsgs -- or a very large one, that would allow me years of runway before hitting any hard limits.

The stream would have a LimitsPolicy and R3 replication.

The numbers we're talking about would be ~ 5M messages stored in one stream per year, amounting to ~0.6GB (considering data and overhead).

What are the practical limitations about this setup? How long before I'd hit a hard limit?

Are there people who have configured streams in such a way, and what were the pitfalls?