Live data from Hacker News

Stream Compression in NATS

qaze.app

21–24 of 24 posts

Re: Stream Compression in NATS

#21
post #18

I was hoping the blog post would include a tentative roadmap for adding tiered storage.

This post is about a product for NATS. I presume you are talking about the roadmap after the 2.10 release?

Yea, after reading the article I went and read the 2.10 release blog post and then came back and commented as if the article posted was the 2.10 post. That was my mistake.

Re: Stream Compression in NATS

#22
post #20
post #19

Earlier quoted context omitted.

Regarding middleware, last time I tried there was a lot of information to process. Now I tried again and func loggingMiddleware(next micro.Handler) micro.Handler { return micro.HandlerFunc(func(req micro.Request) { spew.Dump(req.Data()) next.Handle(req) }) } I'll remove the middleware part. EDIT: Seems I can't edit the post anymore. Regarding auth, yes, spectrum of options, but for "production" use it's very complica…

> You're in your own little bubble and expect people to be mind readers. Out of curiosity, have you asked questions in Slack or Github? If so, and you had a bad experience with the interaction, I get the sentiment and would offer help. But this comment is not constructive without context. > I'm guessing that the documentation is bad so one has to pay for support. The NATS project has been open source for around 12 ye…

It really doesn't help that Slack requires an account, isn't searchable and doesn't preserve history :)

Re: Stream Compression in NATS

#23
post #22
post #20

Earlier quoted context omitted.

> You're in your own little bubble and expect people to be mind readers. Out of curiosity, have you asked questions in Slack or Github? If so, and you had a bad experience with the interaction, I get the sentiment and would offer help. But this comment is not constructive without context. > I'm guessing that the documentation is bad so one has to pay for support. The NATS project has been open source for around 12 ye…

It really doesn't help that Slack requires an account, isn't searchable and doesn't preserve history :)

If a learning resource is lacking or confusing, Slack or GitHub issues/discussions is a way to engage and provide feedback so they can be improved. If the docs were confusing, there are other channels to get help to unblock folks. The outcome of that interaction would lead to improvements in the docs.

Re: Stream Compression in NATS

#24
post #23
post #22

Earlier quoted context omitted.

It really doesn't help that Slack requires an account, isn't searchable and doesn't preserve history :)

If a learning resource is lacking or confusing, Slack or GitHub issues/discussions is a way to engage and provide feedback so they can be improved. If the docs were confusing, there are other channels to get help to unblock folks. The outcome of that interaction would lead to improvements in the docs.

Fair! And I have to say that the docs are pretty good considering the huge surface they cover! Same underlying API, but so many languages.
Post reply on HN