HN823: Defining A Modern Network Service
Network engineer Mark Prosser discusses with host Ethan Banks the need to redefine what constitutes a modern network service, arguing that traditional definitions are inadequate for today's complex, multi-layered networks with overlays, cloud components, and organizational silos. They explore how service validation and testing should be integral to service definition and delivery.
Summary
This Heavy Networking podcast episode features Mark Prosser, a network operator advocate from Nokia and co-founder of Toronto NOG (TorNog), discussing the evolving definition of network services. Prosser argues that while network services were once easily understood as simple configurations like VLANs or BGP peering, modern networks have become significantly more complex with overlays, cloud integrations, and organizational silos that make end-to-end service delivery challenging.
The conversation explores how network services now involve multiple layers of abstraction, often crossing organizational boundaries and involving infrastructure that network teams don't directly control. Prosser emphasizes the importance of systems-level thinking rather than focusing on individual network components, advocating for understanding services as end-to-end outcomes rather than just technical configurations.
A significant portion of the discussion centers on service validation and testing as core components of service definition. Prosser argues that a service cannot truly be considered delivered until it has passed comprehensive validation tests that cover all layers of the network stack. This includes ongoing testing throughout the service lifecycle, not just initial provisioning validation.
The hosts discuss the organizational challenges of modern network service delivery, including the breakdown of collaboration between teams due to increased technical complexity and specialization. They explore how socio-technical systems thinking can help bridge these gaps, emphasizing the need for cross-functional collaboration to deliver business outcomes effectively.
Key Insights
- Prosser argues that modern network services require end-to-end thinking across multiple layers of abstraction rather than focusing on individual network components or configurations
- The speaker contends that organizational silos have become more pronounced as technical domains have grown more complex, making cross-team collaboration harder than in previous eras when network engineers also handled system administration
- Prosser claims that comprehensive service validation and ongoing testing should be considered integral parts of service definition, not separate activities performed after deployment
- The discussion reveals that modern network services often involve infrastructure and overlays that organizations don't directly control, requiring new approaches to service validation and monitoring
- Banks observes that knowledge domains have become more complex over time, with legacy knowledge still required while new technologies continue to be layered on top
- Prosser advocates for treating networks as collections of services with specific business outcomes rather than viewing them as monolithic infrastructures defined by hardware and protocols
- The speakers argue that socio-technical systems thinking is necessary to balance human organizational challenges with technical implementation when delivering modern network services
- Prosser suggests that AI and automation tools can help bridge communication gaps between different technical specialties and reduce the burden of documentation and testing that human teams struggle to maintain
Topics
Full transcript available for MurmurCast members
Sign Up to Access