Skip to content

Commit

Permalink
docs: spell fix for queues
Browse files Browse the repository at this point in the history
spell fix
  • Loading branch information
reddec authored Jul 20, 2020
1 parent 79c8722 commit 91d25bf
Showing 1 changed file with 7 additions and 11 deletions.
18 changes: 7 additions & 11 deletions docs/usage/queues.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,22 +8,18 @@ nav_order: 7

Since `0.3.5`

**this is young feature** - functionality could be dramatically enriched in a future.
**this is young feature** - functionality could be dramatically enriched in the future.

By default, queues stored in a directory-based style. Each element of queue pipes directly from
incoming requests, as well as to lambda without caching. It means - RAM usage is almost constant regardless
of requests sizes and number of elements in a queue.
By default, queues stored in a directory-based style. Each element of queue pipes directly from incoming requests, as well as to lambda without caching. It means - RAM usage is almost constant regardless of request sizes and a number of elements in a queue.

Currently, there are not security restrictions for the queue on append time. All checks will be performed before lambda
execution in same way as it defined in security.
Currently, there are no security restrictions for the queue on append time. All checks will be performed before lambda
execution in the same way as it defined in security.

Queues that bound to the lambda could be found in Overview -> Endpoint page.

Queue can be re-assigned to another lambda without destroy.
A queue can be re-assigned to another lambda without destroying it.

In case of failure, task will be re-tried after defined interval with limited number of attempts. 0 retry means
no **additional attempts** - at least once the task will be processed. After failure, a queue worker will wait required
time, and it will not process other tasks.
In case of failure, the task will be re-tried after a defined interval with a limited number of attempts. 0 retry means no **additional attempts** - at least once the task will be processed. After failure, a queue worker will wait the required time, and it will not process other tasks.

After lambda removal, linked queues are also will be **automatically removed**.

Expand All @@ -37,7 +33,7 @@ NOT designed for

Endpoint: `/q/:queue-name`

Allowed queue name: latin letters, numbers and dash up. From 3 to 64 symbols length.
Allowed queue name: latin letters, numbers, dash, and 3 to 64 symbols length.

One queue always linked to one lambda, but one lambda can be linked to multiple queues.

Expand Down

0 comments on commit 91d25bf

Please sign in to comment.