FAQs

FAQs on Switching

Why is Packet Switching Better for the Internet?

Packet switching is better suited for the modern internet because internet traffic is highly bursty and shared among millions of users.

• Users send data only when needed instead of continuously.

• Network resources are dynamically shared among many users.

• Packet switching avoids permanent bandwidth reservation.

• This improves link utilization and makes the internet more scalable.

Why is Circuit Switching Good for Traditional Voice Calls?

Traditional voice calls need continuous real-time communication with predictable delay.

• Circuit switching creates a dedicated communication path.

• Bandwidth remains reserved for the full call duration.

• Delay is predictable because the path is fixed.

• This provides stable voice quality during the session.

Can Packets Arrive Out of Order?

Yes, packets can arrive out of order in packet-switched networks.

• Different packets may take different paths to the destination.

• Some paths may have more congestion or delay.

• Packets may reach the receiver in a different order from how they were sent.

• Protocols such as TCP use sequence numbers to reorder packets correctly.

Who Handles Packet Loss in Packet Switching?

Packet-switched networks usually work on a best-effort delivery model, so packet loss can happen.

• TCP detects missing packets and retransmits them when needed.

• TCP also handles ordering, flow control, and congestion control.

• UDP does not automatically retransmit lost packets.

• Real-time applications using UDP may tolerate some loss to avoid extra delay.

Is TCP Circuit Switching?

No, TCP is not circuit switching. TCP works over a packet-switched IP network.

• TCP creates a logical connection between two applications.

• The underlying network still sends data as packets.

• No dedicated physical path is reserved.

• Packets may still travel through dynamic routes inside the network.

Why is Message Switching Not Used for Real-Time Communication?

Message switching is not suitable for real-time communication because it introduces high delay.

• Each intermediate node stores the complete message before forwarding it.

• Large messages take more time to receive, store, and forward.

• Every hop adds extra waiting time.

• Real-time applications such as voice and video cannot tolerate this delay.