Designing network systems: bandwidth, requirements, design goals and methodology

Why design matters

Businesses depend on their networks to connect people and run applications around the clock. A network built by plugging in devices without a plan becomes slow, fragile and insecure as it grows. Careful design avoids that.

Bandwidth

Bandwidth is the amount of data a link can carry in a given time, usually measured in bits per second (bps). Over a long enough time you can download anything, but users won't wait forever, so bandwidth must be planned, managed and prioritised like any limited resource. Removing unwanted and duplicated traffic improves response times for everyone.

Why bandwidth matters: it is limited by physics and technology, it costs money, demand keeps growing quickly, and it directly affects how fast the network feels. Note the difference between bits (speeds) and bytes (file sizes): 8 bits = 1 byte. Check transfer times with the download time calculator.

Users and their expectations

Users are the people who use the network within the permissions the administrator gives them. They don't think about the network's complexity; they just expect their applications to work quickly and reliably whenever they need them.

What businesses need from a network

• It stays up all the time, even when a link or device fails or traffic peaks.
• It delivers applications with reasonable response times between any two points.
• It is secure, protecting data in transit and on connected devices.
• It is easy to change as the business grows.
• When problems happen, they are quick to troubleshoot.

Four fundamental design goals

• Scalability: new users, sites and applications can be added without hurting existing users.
• Availability: consistent performance 24/7; a single failed link or device shouldn't take services down.
• Security: planned from the start: where firewalls, filters and segmentation go, not bolted on later.
• Manageability: the IT team can actually run and support it; an over-complicated network fails in practice.

Steps to build a good network

1. Confirm the business goals and technical requirements.
2. Decide the features and functions needed to meet them.
3. Assess whether the existing network is ready.
4. Create the solution and an acceptance test plan.
5. Create a project plan for the rollout.

A three-step design method

1. Identify the requirements. Work with the customer to document business goals (how the network helps the business succeed) and technical requirements (how the technology must work).
2. Characterise the existing network. Collect information about current devices, cabling, addressing, traffic and services; decide what can be reused and what is new.
3. Design the topology and solutions. Use a top-down approach: start from the applications and services needed, then design the network to support them. Test with a prototype or proof of concept before full rollout.

How big is the change?

Real-world example: a primary school's new network

A fictional primary school planned to give every pupil a tablet. Before buying anything, the IT coordinator met the head teacher to agree the business goals: lessons must not stall when thirty tablets stream video at once, and staff data must stay separate from pupil devices. She then studied the existing network and found unmanaged switches, one slow internet line and Wi-Fi access points that covered only half the classrooms. Her design added managed PoE switches, an access point in every classroom, separate VLANs for staff, pupils and guests, and a faster internet line with content filtering. She tested the design with one class for two weeks, adjusted the Wi-Fi channels, and only then rolled it out to the whole school during the summer break.