Skip to content

Fix sentence #1646

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.

Sign up for GitHub

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

Merged
jeremydmiller merged 1 commit into from
Aug 27, 2025
Merged

Fix sentence #1646

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/tutorials/modular-monolith.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ messaging, either locally in process or through external message brokers. Asynch
decoupled, and often leads to much more resilient systems as your modules aren't "temporally" coupled and you utilize
[retry or other error handling policies](/guide/handlers/error-handling) independently on downstream queues.

You can communicate do any mix of in process messaging and messaging through external messaging brokers like Rabbit MQ or Azure Service Bus.
You can communicate with any mix of in process messaging and messaging through external messaging brokers like Rabbit MQ or Azure Service Bus.
Let's start with just using local, in process queueing with Wolverine between your modules as shown below:

![Communicating through local queues](/modular-monolith-local-queues.png)
Expand Down