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

Bootstrap website #15

Merged
merged 11 commits into from
Apr 30, 2024
Merged

Bootstrap website #15

merged 11 commits into from
Apr 30, 2024

Conversation

satabin
Copy link
Collaborator

@satabin satabin commented Apr 19, 2024

This bootstraps the documentation website using Laika integrated in the sbt-typelevel plugin.

  • Getting started
  • Publish
  • Subscribe
  • Adminsitration
  • Serializer/Deserializer
  • SQS
  • Service Bus
  • Circe
  • otel4s

@satabin satabin marked this pull request as ready for review April 29, 2024 14:59
@satabin satabin merged commit 6fa84ff into main Apr 30, 2024
10 checks passed
@satabin satabin deleted the site/bootstrap branch April 30, 2024 13:07
docs/getting-started/queues.md Show resolved Hide resolved
docs/getting-started/subscribing.md Show resolved Hide resolved
project/Website.scala Show resolved Hide resolved
client.subscribe[String]("my-queue")
```

When a message is received by a subscriber, it is _locked_ (or _leased_) for a queue level configured amount of time (see more on the [Managing Queues] page). This means that only one subscriber receives (and can process) a given message in this amount of time. A message needs to be settled once processed (or if processing fails) to ensure it is either removed from the queue or made available again. This is part of the message control flow.

Choose a reason for hiding this comment

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

Suggested change
When a message is received by a subscriber, it is _locked_ (or _leased_) for a queue level configured amount of time (see more on the [Managing Queues] page). This means that only one subscriber receives (and can process) a given message in this amount of time. A message needs to be settled once processed (or if processing fails) to ensure it is either removed from the queue or made available again. This is part of the message control flow.
When a message is received by a subscriber, it is _locked_ (or _leased_) at the queue level for a configured amount of time (see more on the [Managing Queues] page). This means that only one subscriber receives (and can process) a given message in this amount of time. A message needs to be settled once processed (or if processing fails) to ensure it is either removed from the queue or made available again. This is part of the message control flow.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

What I am trying to say here (and below) is that the time for which the lock is held is configured at queue level, and not for each message.

docs/getting-started/subscribing.md Show resolved Hide resolved

1. `MessageContext.ack()` acknowledges the message, and marks it as successfully processed in the queue system. It will be permanently removed and no other subscriber will ever receive it.
2. `MessageContext.nack()` marks the message as not processed, releasing the lock in the queue system. It will be viewable for other subscribers to receive and process.
3. `MessageContext.extendLock()` extends the currently owned lock by the queue level configured duration. This can be called as many times as you want, as long as you still own the lock. As long as the lock is extended, the message will not be distributed to any other subscriber by the queue system.

Choose a reason for hiding this comment

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

Suggested change
3. `MessageContext.extendLock()` extends the currently owned lock by the queue level configured duration. This can be called as many times as you want, as long as you still own the lock. As long as the lock is extended, the message will not be distributed to any other subscriber by the queue system.
3. `MessageContext.extendLock()` extends the currently owned lock at the queue level for a configured duration. This can be called as many times as you want, as long as you still own the lock. As long as the lock is extended, the message will not be distributed to any other subscriber by the queue system.

docs/getting-started/subscribing.md Show resolved Hide resolved
docs/index.md Show resolved Hide resolved
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.

2 participants