Browse Source

Update conclusion on persistent messages and scalability

Added a note about the impact of persistent messages on scalability in the conclusion section.
pull/24637/head
Fahri Gedik 8 months ago
committed by GitHub
parent
commit
675f4783b3
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 3
      docs/en/Community-Articles/2026-01-11/article.md

3
docs/en/Community-Articles/2026-01-11/article.md

@ -148,6 +148,7 @@ Because a synchronous send makes a blocking call until a confirmation is receive
#### 4. Overall Scalability
This is because, upon receipt, the message broker has to spend more time persisting messages to disk, thus negatively affecting scalability. Persistent messages always give lower total throughput, which can limit scalability under high usage loads and high message volumes.
---
## Conclusion
@ -166,4 +167,4 @@ The answers to these questions will help you determine whether the Async Chain o
To see an example project where this pattern is implemented, you can check out the repository:
🔗 **[GitHub Repository](https://github.com/fahrigedik/SoftwareArchitecturePatterns)**
🔗 **[GitHub Repository](https://github.com/fahrigedik/SoftwareArchitecturePatterns)**

Loading…
Cancel
Save