Skip to content

Commit bdb9ff8

Browse files
Bridge hosting (#7198)
1 parent d34751a commit bdb9ff8

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

nservicebus/bridge/index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,12 @@ The messaging bridge enables several scenarios:
2626

2727
More details on these scenarios are provided in the [messaging bridge scenarios](scenarios.md) article.
2828

29+
## Hosting
30+
31+
While it's technically possible to co-host the bridge within the same process as a regular NServiceBus endpoint, it's generally recommended to run the bridge in a dedicated hosting process. The bridge's purpose is purely infrastructural—it connects logical endpoints.
32+
33+
To fulfill this role as efficiently as possible, it may be necessary to scale the bridge either [vertically](performance.md#performance-tuning) or [horizontally](performance.md#scaling-out). Because of its infrastructural nature, the bridge also exhibits significantly different CPU, memory, and monitoring characteristics compared to a typical NServiceBus endpoint that handles business logic.
34+
2935
## Bridge configuration
3036

3137
partial: configuration

0 commit comments

Comments
 (0)