Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/messaging.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Nitric provides two common options for scalable, decoupled, asynchronous messagi

In some circumstances messages sent to a _Topic_ may also be called _Events_, while messages sent to a _Queue_ may be called _Tasks_. The structures of these messages are very similar, but the delivery and retry mechanisms are different. It can be helpful to refer to these messages differently to assist in understanding the context in which they are used.

### Topics
## Topics

A topic is a named resource where events can be published. They can be thought of as a subject that your services are communicating about.

Expand Down Expand Up @@ -360,7 +360,7 @@ updates.subscribe((ctx) async {

You can read more about idempotent subscribers and patterns to handle it [here](https://microservices.io/post/microservices/patterns/2020/10/16/idempotent-consumer.html).

### Queues
## Queues

Queues are another option for asynchronous messaging. Unlike [topics](#topics), messages sent to a queue won't automatically trigger services to process them. Instead, services dequeue message by requesting them.

Expand Down
Loading