Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Resilience Pillar/ HA Design/ RES05 Network HA/ RES05-03 Isolating Network Bandwidth Among Services of Different Traffic Models

Updated on 2025-05-22 GMT+08:00

View PDF

RES05-03 Isolating Network Bandwidth Among Services of Different Traffic Models

If services of different traffic models share network bandwidth, one service can disrupt others through traffic preemption.

Risk level
High
Key strategies
- Services of the same traffic model can share the network bandwidth. The shared bandwidth must satisfy all connected services' needs.
- Use separate bandwidth instances for services with different traffic models to avoid interference.
- Use separate domain names for services with different features.

Parent topic: RES05 Network HA

Previous topic: RES05-02 Avoiding Unnecessarily Exposing Network Addresses

Next topic: RES05-04 Reserving IP Resources for Expansion and HA

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.