You don’t have to look far to see why IT teams are struggling to deliver a reliable user experience across their network. Many networks are overwhelmed by the number of wireless devices connecting to them. It started with the Bring Your Own Device (BYOD) revolution which was accelerated by the birth of the smartphone…a device that didn’t even exist when the pervasive wireless LAN controller technologies were created. Fast forward to today, the Internet of Things (IoT) is now boosting the number of connected devices by an order of magnitude with over 75 billion devices predicted by 2025.
Network reliability engineering demands specific capabilities from your network tooling and the simplicity to be had from a declarative set of tooling makes life so much more pleasant. It’s that feeling when you’re watching the sun set over a blue ocean, sitting on golden sand, drinking fresh pressed mango juice. You know the feeling. It feels like life has taken care of events to allow you to be there and become one with what you’re melting into. By the time you’ve read this post, the hope is that you, too, can enjoy sipping on cool juice whilst watching a glorious day come to a close.
At Juniper Networks, our work is to envision, design and build the network of the future. While that future is surely software-defined and charged with cloud transformation, there is a wide gap between the reality of today’s networks and the cohesive and centrally-managed model of the future. Today, this vision is just starting to take shape and AI sets the stage for the next step where experience is the new uptime.
On the journey to automated network operations, many organizations begin by aligning with internal software development teams and applying lessons learned in the software space to help make network infrastructure and operations more resilient.
One of the most impactful examples is the idea of automated testing. For years, software engineers have used development methodologies like “test-driven development” to keep software quality higher and discover bugs earlier in the software development process, where they can be fixed more easily and cost-effectively. Rather than simply make changes on a whim, developers first commit their operational knowledge of the system into automated tests, which must pass in order for the software to be considered “working”.
Information security must be about far more than simple prevention. Preventing cyberattacks is a critical component of modern information security, however, on its own prevention is inadequate. Understanding dwell time is useful in understanding why.
Networking is complex. There are many protocols running across the various OSI layers that are highly interconnected. Another way of layering includes the management, control and forwarding planes. In network design, we have various layers including the optical, core, spine and edge. Navigating all of this when trying to gather information or make changes can be rather difficult!