{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Cybersecurity Tech Brief By HackerNoon","title":"What It Actually Takes to Network a Live System That's Never Allowed to Go Offline","html":"","width":"100%","height":180,"duration":598,"description":"\n This story was originally published on HackerNoon at: https://hackernoon.com/what-it-actually-takes-to-network-a-live-system-thats-never-allowed-to-go-offline.\nLessons from building transit networks that can never go offline: addressing as a 20-year decision, blast-radius switch design, and testing by breaking things.\nCheck more stories related to cybersecurity at: https://hackernoon.com/c/cybersecurity.\n You can also check exclusive content about #networking, #system-design, #site-reliability-engineering, #infrastructure, #resilience, #building-networks, #public-transit-system, #intercom, and more.\nThis story was written by: @savni. Learn more about this writer by checking @savni's about page,\n and for more stories, please visit hackernoon.com.\nI've spent over a decade building networks for a public transit system that's almost never allowed to go offline — surveillance, public address, intercom, and emergency comms running while trains keep moving underneath. That single \"no maintenance window\" constraint reshapes every decision: addressing schemes become twenty-year commitments, switch configuration becomes a blast-radius problem, and the acceptance test becomes the real deliverable. Here's what mission-critical network engineering actually takes when \"down\" means a passenger presses a call button and nobody answers.","thumbnail_url":"https://img.transistorcdn.com/SySK4I0jwuU6AzeawZdYiDqTq8yzBjxJ5qfTpUuAxEo/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMjY2LzE2ODM1/ODIzNTYtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}