Shifting Even Lefter: Can Infrastructure Help?
October 19, 2016

Barry Phillips
Panzura

DevOps leaders are engaged in an all-out effort to "shift left" so they can deliver better software faster and at lower cost. Much of this effort entails fairly dramatic re-engineering of the dev/test process. And, if we're honest, much of it also entails a management culture of extreme demands on the development and test team.

But while we're building our state-of-the-art DevOps toolchains and pumping our people full of Hint Kick, there may be another smart way to shift even further left:

Re-think build distribution infrastructure.

The Physics of Process

Process and management culture can't overcome the laws of physics. And if you have to share massive builds or artifacts across multiple dev and test teams worldwide—as financial institutions, game developers, and other organizations often do — physics definitely gets in your way.

That's because you have to keep shipping these massive files over the network to those multiple locations again and again as you cycle through your dev/test processes. On the typical enterprise network, that code distribution can take hours.

Consider a 10GB build distributed to five different locations from your primary facility over a 10Mbps MPLS connection. You don't have to be a network expert to do the math. If a couple of your remote locations have 5Mbps connections, it takes them 5 hours to get each build. If three of those locations have 2Mbps connections (as is likely the case in Asia), code distribution takes 12.5 hours.

So the physics of code distribution costs you a day. Repeatedly.

The irony is that the more agile and iterative you try to get in this scenario, the more you pay this distribution time-tax. Conventional code distribution is therefore a primary enemy of the Agile/DevOps "shift left" imperative.

The Shift-Enabling Alternative

The alternative to conventional ship-it-over-the-network-and-wait-a-day approach to build distribution is a hub-and-spoke model that allows you to lets you maintain a "gold copy" of your current codebase(s) in the cloud — while providing all your remote locations with their own local copies that get continuously and automatically updated with any changes as they occur.

This model eliminates network-related bottlenecks while allowing your geographically dispersed teams to collaborate without tripping over each other's work.

The result: You can shift left much more aggressively, without the constant counter-productive impediment of a network that can't deliver your builds fast enough to your entire team.

Of course, if you're leading the shift-left efforts at your company, you probably don't own your company's IT infrastructure. So you'll have to make your case to whoever does.

But it's a worthwhile effort. Hub-and-spoke code distribution gives software-intensive businesses competitive advantage by dramatically accelerating time-to-market for digital deliverables—while ensuring that test/QA rigor doesn't unnecessarily delay that delivery. It also saves infrastructure owners lots of money in storage, bandwidth costs and network acceleration hardware.

So if you want to shift left — but keep running into a chronic network bottleneck — have that conversation today. It'll be a win-win for your business and your budget!

Barry Phillips is CMO of Panzura.

The Latest

July 19, 2018

Despite 95 percent of CIOs expecting cyberthreats to increase over the next three years, only 65 percent of their organizations currently have a cybersecurity expert, according to a survey from Gartner. The survey also reveals that skills challenges continue to plague organizations that undergo digitalization, with digital security staffing shortages considered a top inhibitor to innovation ...

July 17, 2018

In my first blog in this series, I highlighted some of the main challenges teams face with trying to scale mainframe DevOps. To get past these hurdles, the key is to develop an incremental approach that enables teams to capture value along each step of the journey ...

July 16, 2018

The key to mainframe DevOps success is in quickly identifying and removing major bottlenecks in the application delivery lifecycle. Major challenges include collaboration between mainframe and distributed teams, lack of visibility into the impact of software changes, and limited resource flexibility with scaling out necessary testing initiatives. Now let's take a closer look at some of these key challenges and how IT departments can address them ...

July 11, 2018

How much are organizations investing in the shift to cloud native, how much is it getting them? ...

July 10, 2018

In the shift to cloud native, many organizations have adopted a configuration-as-code approach. This helps drive up application deployment velocity by letting developers and DevOps teams reconfigure their deployments as their needs arise. Other organizations, particularly the more regulated ones, still have security people owning these tools, but that creates increased pressure on the security organization to keep up. How much are organizations investing in this process, and how much is it getting them? ...

June 28, 2018

More than a third of companies that use serverless functions are not employing any application security best practices and are not using any tools or standard security methodologies to secure them, according to the State of Serverless Security survey, conducted by PureSec ...

June 27, 2018

The popularity of social media platforms and applications is spurring enterprises to adopt "social business" models to better engage with employees and customers and improve collaboration, according to a new study published by ISG ...

June 25, 2018

The previous chapter in this WhiteHat Security series discussed Codebase as the first step of the Twelve-Factor App and defined a security best practice approach for ensuring a secure source control system. Considering the importance of applying security in a modern DevOps world, this next chapter examines the security component of step two of the Twelve-Factor methodology. Here follows some actionable advice from the WhiteHat Security Addendum Checklist, which developers and ops engineers can follow during the SaaS build and operations stages ...

June 21, 2018

DevSecOps is quickly gaining support and traction, within and beyond information security teams. In fact, 70% of respondents believe their culture can embrace the change needed to fuse Security and DevOps, according to a new survey of 80 security professionals by Aqua Security ...

June 20, 2018

The larger the company size, the higher the proportion of low IT performers, according to the State of DevOps: Market Segmentation Report from Puppet, based on the 2017 State of DevOps Survey data ...

Share this