HN823: Defining A Modern Network Service
Get the full intelligence
Search transcripts, export clips, track mentions, and explore all topics from “HN823: Defining A Modern Network Service” inside PodZeus.
In this episode of Heavy Networking, host Ethan Banks sits down with Mark Prosser, network operator advocate and founder of Tornog, a Toronto-based network operators group, to explore the evolving definition of a 'network service' in the modern era. The conversation centers on how the complexity of today’s networks—driven by overlays, cloud integration, outsourced infrastructure, and AI—has made traditional service provisioning inadequate. Mark argues that a true network service must be end-to-end, validated across all layers, and understood holistically across organizational boundaries. He emphasizes that service delivery is no longer just about configuration but about business outcomes, compliance, and continuous validation. The discussion highlights the growing disconnect between technical teams, the rise of silos, and the need for sociotechnical systems thinking. Ethan and Mark also explore the challenges of testing in dynamic environments, the limitations of tribal knowledge, and the potential of AI and tools like NUTS and PyATS to bridge gaps in documentation and observability. The episode concludes with a call to action: organizations must start small, document services iteratively, and prioritize collaboration to deliver resilient, measurable network services in an age of relentless complexity. Key takeaways include: 1) A network service must be defined by its end-to-end impact on business outcomes, not just technical configuration; 2) Continuous validation and testing—beyond initial deployment—are essential due to dynamic network conditions; 3) Organizational silos hinder service delivery, and teams must adopt systems-level thinking and cross-functional collaboration; 4) Tools like NUTS and PyATS can help automate testing, but the real challenge is cultural and process-oriented; 5) AI can assist in generating documentation and translating technical jargon across teams, reducing friction; 6) Start small—focus on the 20% of testing that delivers 80% of value—and iterate; 7) The network is no longer a monolithic entity but a collection of interdependent services requiring shared ownership; 8) Human insight remains irreplaceable, even as automation and AI advance.
A network service must be defined by its end-to-end impact on business outcomes, not just technical configuration.
Continuous validation and testing—beyond initial deployment—are essential due to dynamic network conditions.
Organizational silos hinder service delivery, and teams must adopt systems-level thinking and cross-functional collaboration.
Tools like NUTS and PyATS can help automate testing, but the real challenge is cultural and process-oriented.
AI can assist in generating documentation and translating technical jargon across teams, reducing friction.
…and 3 more takeaways available in PodZeus
Sponsor: Meter Network-as-a-Service
Ethan introduces the episode's sponsor, Meter, a network-as-a-service provider offering integrated wired, wireless, and cellular solutions delivered as a managed service. Meter handles hardware provisioning, upgrades, monitoring, and site setup, reducing operational overhead.
Introducing Mark Prosser and Tornog
Ethan welcomes Mark Prosser, founder of Tornog—a Toronto-based network operators group—discussing its growth, mission, and the broader need for regional NOGs across Canada. Mark shares insights on community building and the challenges of organizing in rural areas.
The Evolving Definition of a Network Service
“A real service is end-to-end. It's many layers of abstraction. But cars have a lot of congestion. Is the service really servicing the applications or the business outcomes? That's what I'm seeing people aren't really thinking about.”
From Lego Bricks to Sociotechnical Systems
“The concept of a socio-technical system essentially is this concept where there's a balance between the socio, i.e. the humans and all of our faults and delicacies in life, and then the technical parts...”
The Testing and Validation Imperative
“You don't know what tests you need until your service, until you passed all your tests but the service still isn't working and then you go back and get a test. So there is a cycle that you have to go through.”
“If you think it's elephant flows, get out of the room. I need something with a different thought pattern.”
“A real service is end-to-end. It's many layers of abstraction. But cars have a lot of congestion. Is the service really servicing the applications or the business outcomes? That's what I'm seeing people aren't really thinking about.”
“Start small—focus on the 20% of testing that delivers 80% of value—and iterate.”
Host
Guest
Ethan Banks
person
Mark Prosser
person
Tornog
organization
Meter
organization
Nanog 96
other
Packet Pushers
other
NUTS
product
SD-WAN
other
PyATS
product
Kubernetes
other
PP103: FireMon Brings Clarity to Firewall Rule Chaos (Sponsored)
The Everything Feed - All Packet Pushers Pods • 56m • 3/31/2026
HW074: Build Your Own Access Point with Bradley Wegner
The Everything Feed - All Packet Pushers Pods • 26m • 3/31/2026
NAN118: The Importance of the Data Behind AI in Networks (Sponsored)
The Everything Feed - All Packet Pushers Pods • 43m • 4/1/2026
D2DO299: The State of Platform Engineering and DevEx
The Everything Feed - All Packet Pushers Pods • 43m • 4/1/2026
N4N052: Multicast Part 2
The Everything Feed - All Packet Pushers Pods • 1h 25m • 4/2/2026
Get the full intelligence
Search transcripts, export clips, track mentions, and explore all topics from “HN823: Defining A Modern Network Service” inside PodZeus.
Start discovering podcast insights today
Start with a 7-day trial and explore a growing catalog of popular podcasts. No credit card required.
No credit card required • 7-day trial • Cancel anytime
