Welcome!

SDN Journal Authors: Liz McMillan, Yeshim Deniz, Elizabeth White, Pat Romanski, TJ Randall

Related Topics: SDN Journal, Java IoT, Microservices Expo, Linux Containers, Containers Expo Blog, @CloudExpo

SDN Journal: Blog Feed Post

Timing Technological Change: Creation vs. Consumption

Most people nod their heads when there is talk about programmability, APIs, and massive automation frameworks

In any space, there is a very small vocal minority. Most people lack the time, interest, or even confidence to say what they think in public. So we are left with a vocal few who drive the conversation. In networking, the vocal minority consists mainly of the vanguards for change. For these people, the network is more than just some connective tissue inside a nebulous infrastructure. It is their life. They live and breathe it. Accordingly, they have strong opinions about how things work and, more importantly, how they ought to work.

But what is happening now is that we are at some risk of the luminaries creating an impassable distance between their vision and the on-the-ground reality in many IT shops today.

Most people nod their heads when there is talk about programmability, APIs, and massive automation frameworks. But head-nodding should not be mistaken for agreement and support. It simply shows an understanding of the argument. It can mean anything from “Oh my god! Let’s start right now. Where do I sign the PO?” to “Your logic is sound. You are really smart. Where did I put my Cat6k?”

When you look at the large, web-scale properties, the need for customization and the desire for a DIY environment is huge. These guys simply cannot operate in an environment that is as costly or difficult to manage as what most companies have today. This is why companies like Google have embraced SDN and white box switching from the outset. They stand up in front of conference crowds and talk about what they have done.

And everyone nods their heads.

But let’s be clear: not everyone is Google. Even if their needs were the same, they aren’t printing enough money to make hiring a whole new team feasible. They live in a different reality.

The truth is that there is no inherent nobility in what we build. Whether your environment is massive and complex, or small and simple, all any of us is really trying to do is support our business. If our business requires that we build something sophisticated, we will go and build it. But there are a precious few jobs where sophistication itself is the goal. So barring the work done in professional labs or academia, the vast majority of our market consists of people whose objective is really straightforward: make my business work.

This creates an interesting dynamic. The industry dialogue is dominated by the newest and most sophisticated technologies while the industry buying motions are dominated by the same legacy solutions that have been popular for several decades. I don’t mean to suggest that legacy players can rest on their laurels, but the transition from an aging environment to a newfangled one is not so easy (or even a priority) for many companies. And the further out ahead of demand that vendors go, the more difficult it is to bring customers along.

Make no mistake about it: there will be vendors who overshoot. They will reach too far, convinced that the future is changing. They will be right. But they will be early. The question for these vendors is whether they have the funds to wait for the market to catch up.

This means that vendors in this space have to be worried about more than just getting the technology right – they must also get the timing right. Show up too late, and you are obsolete before you hit the market. Show up too early, and you end up going out of business before the market adopts the technology.

Ultimately, for companies to be successful, they need to be a part of important technology trends while not creating too much distance between themselves and the market. But how do you thread that needle?

The key is in creating a solid technological foundation (you cannot risk obsolescence) from which you can apply an intuitive approach (make it easily adoptable). There is just as much skill in making technology consumable as there is in willing it into existence. Innovation is more than just exposing a bunch of capabilities through APIs and configuration knobs. You need to make those capabilities relevant and easy-to-use in context.

This is partly why OpenFlow has an adoption problem. Tons of capability, but very difficult to use. And it’s not just OpenFlow. If you look at a lot of the edge policy features popular in service provider environments, or complex traffic engineering setups, or even elaborate QoS schemes… they all suffer from a general lack of intuitiveness. Unless the network is your business, you don’t have the time or desire to sift through it all and figure out the arcane bits and pieces.

This should be instructive. As new companies attack the network, they need to be emphasizing more than just functionality. Those that address both the creation and consumption of technology will be uniquely positioned to take advantage of the vocal minority while servicing the buying majority.

[Today’s fun fact: An office chair with wheels travels 8 miles a year.]

The post Timing technological change: creation vs. consumption appeared first on Plexxi.

Read the original blog entry...

More Stories By Michael Bushong

The best marketing efforts leverage deep technology understanding with a highly-approachable means of communicating. Plexxi's Vice President of Marketing Michael Bushong has acquired these skills having spent 12 years at Juniper Networks where he led product management, product strategy and product marketing organizations for Juniper's flagship operating system, Junos. Michael spent the last several years at Juniper leading their SDN efforts across both service provider and enterprise markets. Prior to Juniper, Michael spent time at database supplier Sybase, and ASIC design tool companies Synopsis and Magma Design Automation. Michael's undergraduate work at the University of California Berkeley in advanced fluid mechanics and heat transfer lend new meaning to the marketing phrase "This isn't rocket science."

CloudEXPO Stories
Sanjeev Sharma Joins November 11-13, 2018 @DevOpsSummit at @CloudEXPO New York Faculty. Sanjeev Sharma is an internationally known DevOps and Cloud Transformation thought leader, technology executive, and author. Sanjeev's industry experience includes tenures as CTO, Technical Sales leader, and Cloud Architect leader. As an IBM Distinguished Engineer, Sanjeev is recognized at the highest levels of IBM's core of technical leaders.
DXWorldEXPO LLC announced today that Kevin Jackson joined the faculty of CloudEXPO's "10-Year Anniversary Event" which will take place on November 11-13, 2018 in New York City. Kevin L. Jackson is a globally recognized cloud computing expert and Founder/Author of the award winning "Cloud Musings" blog. Mr. Jackson has also been recognized as a "Top 100 Cybersecurity Influencer and Brand" by Onalytica (2015), a Huffington Post "Top 100 Cloud Computing Experts on Twitter" (2013) and a "Top 50 Cloud Computing Blogger for IT Integrators" by CRN (2015). Mr. Jackson's professional career includes service in the US Navy Space Systems Command, Vice President J.P. Morgan Chase, Worldwide Sales Executive for IBM and NJVC Vice President, Cloud Services. He is currently part of a team responsible for onboarding mission applications to the US Intelligence Community cloud computing environment (IC ...
When applications are hosted on servers, they produce immense quantities of logging data. Quality engineers should verify that apps are producing log data that is existent, correct, consumable, and complete. Otherwise, apps in production are not easily monitored, have issues that are difficult to detect, and cannot be corrected quickly. Tom Chavez presents the four steps that quality engineers should include in every test plan for apps that produce log output or other machine data. Learn the steps so your team's apps not only function but also can be monitored and understood from their machine data when running in production.
The best way to leverage your Cloud Expo presence as a sponsor and exhibitor is to plan your news announcements around our events. The press covering Cloud Expo and @ThingsExpo will have access to these releases and will amplify your news announcements. More than two dozen Cloud companies either set deals at our shows or have announced their mergers and acquisitions at Cloud Expo. Product announcements during our show provide your company with the most reach through our targeted audiences.
When building large, cloud-based applications that operate at a high scale, it's important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. "Fly two mistakes high" is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.