Welcome!

Microservices Expo Authors: Harry Trott, Pat Romanski, Steve Wilson, Jason Bloomberg, Stackify Blog

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

SDN Journal: Article

DIY vs DIFY Networking

If you were to base your guess on industry chatter, you would have to conclude that DIY has the upper hand

There is probably never going to be a perfect balance in the industry between Do-it-yourself (DIY) and Do-it-for-you (DIFY) networking. It seems exceedingly unlikely that there is a one-size-fits-all type of solution out there. And so we will invariably end up with a bifurcated market that requires multiple solutions for its constituents. But if there is not a perfect balance, which one of these is likely to see the most action?

If you were to base your guess on industry chatter, you would have to conclude that DIY has the upper hand.

There is a ton of momentum right now with both SDN and bare metal switching. On the SDN front, it is all about orchestration and automation. The ability to streamline customized workflows is attractive, especially for the large IT shops that sink tens of millions of dollars into managing their monstrosities. Once you get into anything that is customized, there is a degree of DIY-ness that is required. No product is designed expressly for your particular environment, so you need to the ability to customize what you buy to do what you want. Beyond that, there is an awful lot of talk about APIs and programmability.

Bare metal switching is a different initiative with different objectives that end up in a similar DIY framework. The move towards a more server-like environment allows users to customize their switching solution. There is great power in having absolute control over how a device behaves. It allows users to pick and choose tools they are already familiar with, extending their functionality into the networking realm.

However, the challenge in using industry dialogue to conclude where things will end up is that the chatter does not always match exactly the buying patterns. Indeed, public discourse most typically leads broad deployment – sometimes by several years or more (think IPv6, Internet of Things, or even electric vehicles).

The DIY movement in networking is real, but what is it about? The ability to tailor specific networking applications to the infrastructure is about eking out performance or customizing experience. It is about modifying a base set of functionality to fit better into your specific context.

For this to matter, you have to be pushing the envelope in terms of performance or capability. But the truth is that the bulk of the networking space is simply not there. Their issues are not in customization. They want to be spending less time with the network, not more. The problem they need solved is more about operating their infrastructure and less about creating substrates to connect it all together in some unique configuration.

But you don’t hear from these people in industry forums and on social media. They lack the interest, time, and sometimes confidence to express a point of view that is less visionary and more functional. As a result, we only hear one side of the story. It plays out in blogs, on Twitter, in press articles, and on conferences stages. And with every word and unapproachable idea, we collectively push the majority of users further into the background.

The solution here isn’t to retreat from change. But we need to make sure that new technology is usable for the legions of people for whom the network is primarily a means of enabling their business. We need to advance with equal enthusiasm DIFY networking.

So why don’t we do this naturally as an industry?

There are two major dynamics at play. First, incumbents tend to be capability-driven. Customer X needs something, so they build whatever widget is required. The focus is on the capability, not necessarily on how that capability is inserted into a widely consumable workflow. If there is any doubt here, ask yourself if networking workflows today are more arcane or intuitive. And then ask yourself why certifications are so important. The only way to validate that you have mastered the arcane is to produce your certificate as proof.

The second dynamic is that new initiatives (be they new companies or just new projects) tend to target the hot spots. Those hot spots are identified by the vocal minority. And networking’s vocal bunch consists of strong proponents for customization, primarily through tooling and development frameworks.

But even here, customization is rarely the outright goal. Unless your business requires differentiated network services (a la service or cloud providers), you likely don’t want to be customized for the sake of being customized. Rather, the customization trends are a response to a broad deficiency in the networking industry. More directly, if my vendor cannot give me what I need, at least give me the tools so I can do it myself.

Both SDN and white box switching are great movements, but they are responses to a long-time issue with legacy networks: the equipment is needlessly expensive, and networks are ridiculously hard to manage. When these issues go unaddressed for decades, what are customers to do? They stand up and collectively say “Screw it. I’ll do it myself.”

When the DIY trends exist long enough, we end up fooling ourselves into thinking customization is the goal when all along it was merely a workaround. We replace intuitive networking with There’s an API for that networking. Essentially, we have shifted the cost from procurement (you can buy cheaper equipment) to development (but you have to customize everything around it).

This doesn’t seem right. I suspect the right outcome for the industry is to take the technological advances, develop them to completeness, and deliver an infrastructure that delivers. Such an infrastructure could still have the hooks for the DIYers, but it would be functional for the DIFYers as well.

[Today’s fun fact: If all of the oceans in the world evaporated, Hawaii would be the tallest mountain in the world. Take that, Everest!]

The post DIY vs DIFY networking appeared first on Plexxi.

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."

@MicroservicesExpo Stories
As many know, the first generation of Cloud Management Platform (CMP) solutions were designed for managing virtual infrastructure (IaaS) and traditional applications. But that’s no longer enough to satisfy evolving and complex business requirements. In his session at 21st Cloud Expo, Scott Davis, Embotics CTO, will explore how next-generation CMPs ensure organizations can manage cloud-native and microservice-based application architectures, while also facilitating agile DevOps methodology. He wi...
There are several reasons why businesses migrate their operations to the cloud. Scalability and price are among the most important factors determining this transition. Unlike legacy systems, cloud based businesses can scale on demand. The database and applications in the cloud are not rendered simply from one server located in your headquarters, but is instead distributed across several servers across the world. Such CDNs also bring about greater control in times of uncertainty. A database hack ...
These days, change is the only constant. In order to adapt and thrive in an ever-advancing and sometimes chaotic workforce, companies must leverage intelligent tools to streamline operations. While we're only at the dawn of machine intelligence, using a workflow manager will benefit your company in both the short and long term. Think: reduced errors, improved efficiency and more empowered employees-and that's just the start. Here are five other reasons workflow automation is leading a revolution...
We define Hybrid IT as a management approach in which organizations create a workload-centric and value-driven integrated technology stack that may include legacy infrastructure, web-scale architectures, private cloud implementations along with public cloud platforms ranging from Infrastructure-as-a-Service to Software-as-a-Service.
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
While some vendors scramble to create and sell you a fancy solution for monitoring your spanking new Amazon Lambdas, hear how you can do it on the cheap using just built-in Java APIs yourself. By exploiting a little-known fact that Lambdas aren’t exactly single-threaded, you can effectively identify hot spots in your serverless code. In his session at @DevOpsSummit at 21st Cloud Expo, Dave Martin, Product owner at CA Technologies, will give a live demonstration and code walkthrough, showing how ...
Did you know that you can develop for mainframes in Java? Or that the testing and deployment can be automated across mobile to mainframe? In his session and demo at @DevOpsSummit at 21st Cloud Expo, Dana Boudreau, a Senior Director at CA Technologies, will discuss how increasingly teams are developing with agile methodologies, using modern development environments, and automating testing and deployments, mobile to mainframe.
Cloud adoption is often driven by a desire to increase efficiency, boost agility and save money. All too often, however, the reality involves unpredictable cost spikes and lack of oversight due to resource limitations. In his session at 20th Cloud Expo, Joe Kinsella, CTO and Founder of CloudHealth Technologies, tackled the question: “How do you build a fully optimized cloud?” He will examine: Why TCO is critical to achieving cloud success – and why attendees should be thinking holistically ab...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
@DevOpsSummit at Cloud Expo taking place Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center, Santa Clara, CA, is co-located with the 21st International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is ...
With Cloud Foundry you can easily deploy and use apps utilizing websocket technology, but not everybody realizes that scaling them out is not that trivial. In his session at 21st Cloud Expo, Roman Swoszowski, CTO and VP, Cloud Foundry Services, at Grape Up, will show you an example of how to deal with this issue. He will demonstrate a cloud-native Spring Boot app running in Cloud Foundry and communicating with clients over websocket protocol that can be easily scaled horizontally and coordinate...
Docker is on a roll. In the last few years, this container management service has become immensely popular in development, especially given the great fit with agile-based projects and continuous delivery. In this article, I want to take a brief look at how you can use Docker to accelerate and streamline the software development lifecycle (SDLC) process.
DevOps at Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 21st Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to w...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
IT organizations are moving to the cloud in hopes to approve efficiency, increase agility and save money. Migrating workloads might seem like a simple task, but what many businesses don’t realize is that application migration criteria differs across organizations, making it difficult for architects to arrive at an accurate TCO number. In his session at 21st Cloud Expo, Joe Kinsella, CTO of CloudHealth Technologies, will offer a systematic approach to understanding the TCO of a cloud application...
API Security has finally entered our security zeitgeist. OWASP Top 10 2017 - RC1 recognized API Security as a first class citizen by adding it as number 10, or A-10 on its list of web application vulnerabilities. We believe this is just the start. The attack surface area offered by API is orders or magnitude larger than any other attack surface area. Consider the fact the APIs expose cloud services, internal databases, application and even legacy mainframes over the internet. What could go wrong...
The goal of Continuous Testing is to shift testing left to find defects earlier and release software faster. This can be achieved by integrating a set of open source functional and performance testing tools in the early stages of your software delivery lifecycle. There is one process that binds all application delivery stages together into one well-orchestrated machine: Continuous Testing. Continuous Testing is the conveyer belt between the Software Factory and production stages. Artifacts are m...
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
In his session at @DevOpsSummit at 20th Cloud Expo, Kelly Looney, director of DevOps consulting for Skytap, showed how an incremental approach to introducing containers into complex, distributed applications results in modernization with less risk and more reward. He also shared the story of how Skytap used Docker to get out of the business of managing infrastructure, and into the business of delivering innovation and business value. Attendees learned how up-front planning allows for a clean sep...
Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...