-
Notifications
You must be signed in to change notification settings - Fork 116
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.
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
README suggestion #152
Comments
naming is very important in software. for some reason, NATS has many inconsistencies and breaks the rules and doesn't care to fix it for long periods of time. |
Agreed 100% Also things like:
make the transition between the two very obnoxious. It is the case that I have a lot of code that uses/manages/creates nats connections already, and I have to go and update all of those just to change imports. |
Not sure what you mean by that. But yes, in general I agree it's confusing. NATS and NATS Streaming are entirely separate systems. We are going to work on clarifying that. Wally's recent ATO talk does a good job of presenting the difference I think: https://www.slideshare.net/wallyqs/nats-simple-secure-and-scalable-messaging-for-the-cloud-native-era-81170151 |
I didn't realize that I will update my imports properly. Thanks for the quick response! |
Hi,
go-nats-streaming
is the Go client for https://github.com/nats-io/nats-streaming-server ? is that correct? if so, please mention that in the README. The description nor README mention its a client for specifically the nats streaming server.Side note: I wish you guys stuck with the project name of "stan". And renamed this repo to
go-stan
andnats-streaming-server
tostan-server
The text was updated successfully, but these errors were encountered: