IT departments are increasingly focused on major technological innovations that ultimately require frequent network infrastructure upgrades. Just look at the growing prominence of IoT, edge computing and software-defined networks. But according to Enterprise Management Associates, navigating the complexity of network architecture and attempting to scale or expand infrastructure are two of the top challenges for businesses when dealing with their networks. The problem: when networks aren't built to scale, emerging technologies end up out-pacing current network capacities, adding unnecessary cost and complexity.
Network Packet Brokers play a critical role in gaining visibility into these new complex networks. They deliver the packet data and information IT and security teams need to identify problems, recognize security issues, and ensure overall network performance. However, not all Packet Brokers are created equal when it comes to scalability. Simply "scaling up" your network infrastructure at every growth point is a more complex and more expensive endeavor over time — cutting into business profitability and productivity. Instead, building network architectures that can "scale out" — quickly adding ports, changing speeds or capabilities — is often a better approach.
Let's explore three ways the "scale up" approach to infrastructure growth impedes NetOps and security professionals (and the business as a whole). Based on these shortcomings, we can then dive into the benefits of scale-out visibility, which can help organizations grow when new technology initiatives alter network requirements.
1. Hardware Investments
When it comes to network infrastructure (including Packet Brokers), the "scale up" approach for hardware often includes buying a big box solution with a bazillion ports. Those ports get used as needed (which often translates to just a small fraction of them), while the unused ports sit idle for "future use" — a simple but wasteful growth solution. With networks growing at a faster rate than budgets these days, investing in idle-assets is often sub-optimal.
The other "scale up" approach is to purchase only the unit that matches today's exact needs, and then when required, decommission the existing unit and buy the next model up. Vendors like to promote the "product family" idea as scaling up. For example, if you purchase the X-1 now, you can later purchase the X-2, X-3, X-4 when you need more ports or power. This family scaling certainly can keep the customer loyal to a vendor by providing a simple upgrade path with familiar operation and management, but it's also wasteful as the smaller product is usually replaced well before the end of its useful life.
For many organizations, a better approach is to "scale out." Buy a smaller base unit that meets your immediate needs and build incrementally as you grow. This includes purchasing a right-sized base unit for initial requirements (call it the "mothership" appliance), then transparently adding on to the initial purchase as growth requires with modules that easily integrate (and leverage the intelligence of the "mothership" unit). This approach protects budget disciplined teams, while still providing a path for seamless (and less disruptive) growth in the future. The IT stakeholder no longer has to pay for something it might use in the future or purchase expensive new appliances along the way.
When you consider that the average end-user interacts with at least 8 applications, then think about how important those applications are in the overall success of the business and how often the interface between the application and the hardware needs to be updated, it's a potential minefield for business operations. Any single update could explode in your face at any time ...
Despite the efforts in modernizing and building a robust infrastructure, IT teams routinely deal with the application, database, hardware, or software outages that can last from a few minutes to several days. These types of incidents can cause financial losses to businesses and damage its reputation ...
In Episode 7, Will Cappelli, Field CTO of Moogsoft and Former Gartner Research VP, joins the AI+ITOPS Podcast to discuss the future of APM, AIOps and Observability ...
Mark Thiele on the AI+ITOPS Podcast: "I believe AIOps will be everywhere, or you will be failing if you're attempting to do scale ..."