Skip to content
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

adding JetStream Docs #178

Merged
merged 32 commits into from
Mar 15, 2021
Merged

adding JetStream Docs #178

merged 32 commits into from
Mar 15, 2021

Conversation

gcolliso
Copy link
Member

No description provided.

@ColinSullivan1 ColinSullivan1 mentioned this pull request Jan 28, 2021
10 tasks
Signed-off-by: Colin Sullivan <colin@synadia.com>
Signed-off-by: Colin Sullivan <colin@synadia.com>
Signed-off-by: Colin Sullivan <colin@synadia.com>
In terms of deployment, a JetStream server is simply a NATS server with the JetStream subsystem enabled, launched with the `-js` flag with a configured server name and cluster name. From a client perspective, it does not matter which servers are running JetStream so long as there is some route to a JetStream enabled server or servers. This allows for a flexible deployment which to optimize resources for particular servers that will store streams versus very low overhead stateless servers, reducing OpEx and ultimately creating a scalable and manageable system.

## Feature List
- At-least-once delivery; exactly once within a window
Copy link

@bwerthmann bwerthmann Feb 5, 2021

Choose a reason for hiding this comment

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

@ColinSullivan1 Q for my understanding more than anything...

These lines for NATS Delivery Guarantees read:

At most once, at least once, and exactly once is available in Jetstream.

Should it be updated to...

...exactly once within a window... (with jetstream)

Copy link
Member

Choose a reason for hiding this comment

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

Thanks! Will do!

gcolliso and others added 4 commits February 9, 2021 16:50
Signed-off-by: Colin Sullivan <colin@synadia.com>
Signed-off-by: Colin Sullivan <colin@synadia.com>
ColinSullivan1 and others added 6 commits February 28, 2021 14:44
Signed-off-by: Colin Sullivan <colin@synadia.com>
Signed-off-by: Colin Sullivan <colin@synadia.com>
Signed-off-by: Colin Sullivan <colin@synadia.com>
In terms of deployment, a JetStream server is simply a NATS server with the JetStream subsystem enabled, launched with the `-js` flag with a configured server name and cluster name. From a client perspective, it does not matter which servers are running JetStream so long as there is some route to a JetStream enabled server or servers. This allows for a flexible deployment which to optimize resources for particular servers that will store streams versus very low overhead stateless servers, reducing OpEx and ultimately creating a scalable and manageable system.

## Feature List
- At-least-once delivery; exactly once within a window
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- At-least-once delivery; exactly once within a window
- At-least-once delivery and exactly once within a window

@gcolliso gcolliso merged commit 3429cc7 into master Mar 15, 2021
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