Why "Scaling Up" Your Network Infrastructure Always Leads to More Complexity and Cost - Part 1
March 18, 2019

Alastair Hartrup
Network Critical

Share this

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.

Read Why "Scaling Up" Your Network Infrastructure Always Leads to More Complexity and Cost - Part 2

Alastair Hartrup is CEO of Network Critical
Share this

The Latest

May 21, 2020

As cloud computing continues to grow, tech pros say they are increasingly prioritizing areas like hybrid infrastructure management, application performance management (APM), and security management to optimize delivery for the organizations they serve, according to ...

May 20, 2020

Businesses see digital experience as a growing priority and a key to their success, with execution requiring a more integrated approach across development, IT and business users, according to Digital Experiences: Where the Industry Stands ...

May 19, 2020

Fully 90% of those who use observability tooling say those tools are important to their team's software development success, including 39% who say observability tools are very important ...

May 18, 2020

As our production application systems continuously increase in complexity, the challenges of understanding, debugging, and improving them keep growing by orders of magnitude. The practice of Observability addresses both the social and the technological challenges of wrangling complexity and working toward achieving production excellence. New research shows how observable systems and practices are changing the APM landscape ...

May 14, 2020
Digital technologies have enveloped our lives like never before. Be it on the personal or professional front, we have become dependent on the accurate functioning of digital devices and the software running them. The performance of the software is critical in running the components and levers of the new digital ecosystem. And to ensure our digital ecosystem delivers the required outcomes, a robust performance testing strategy should be instituted ...