|By Derick Winkworth||
|August 13, 2014 09:00 AM EDT||
We’ve spent some cycles talking about user experience and workflow in previous articles. So in this post, we’re going to explore how these things relate to one another in the context of networking. We’ll talk a little about each separately, then we’ll bring it together in the end.
User Experience (UX), in networking is a tricky thing. It’s not just about the direct user interaction of a particular feature or of a particular product. Over at Packet Pushers, we see many blog entries reviewing network products. Time and time again, they show us that UX encompasses something much broader: It’s the experience of how well the vendor delivers the product, not just the product itself. Vendors must consider the user’s experience from the first interactions with the company, to the unboxing of the product, the ease of finding and consuming relevant documentation, through the actual support process.
Network Engineers expect that there will be problems. However, problems frequently mean one-offs and exceptions until an appropriate fix surfaces. If we can never find an answer in documentation, this can be frustrating. Especially if we are told by support that it is a well known issue. If it’s well known, then produce some documentation with workarounds! If there is an associated bug, put a bug ID in the docs. If possible, put a target release for an upcoming fix, too. Easy to find, relevant documentation can vastly improve the experience of the product, even when dealing with bugs.
Let’s consider the UX of support. On average, your users frequently know more about networking than you do. Customers have poured a significant amount of their time into memorizing piles and piles of facts about how every tiny thing in networking should work. Standards are tricky thing, too. If you are going to tell the customer that your product is “behaving according to standards” then you better be prepared to back that up. You also should be prepared to back down from that argument as well. There are many standards, and portions of standards, that are not followed by any vendor or community in practice. Sometimes standards are not clear or they are contradictory. In these cases, over time, implementations have evolved a certain way to deal with these inconsistencies in order to ensure interoperability. It is incumbent upon the vendor to adjust as required in these situations. Remember the Robustness Principle in RFC 1122 (section 1.2.2): “Be liberal in what you accept, and conservative in what you send.”
The most important part here is that the user’s experience of the company is more important than just the product alone. Vendors should understand all points of interaction with the customer from sales, to documentation, the product user interface, to support, should be crafted relative to the workflow of their customer. Focus less on features, and more on solving problems.
We’ve spent some time, in particular, talking about workflow here on the Plexxi blog site. The first, and key, take away here is that Network Engineering is workflow dominated. Everything we do ends up being a series of steps, and those steps don’t always involve direct interaction with the product. The second takeaway is that workflows are dynamic. As previously discussed, referential space in networking is enormously complicated. Exactly where a network engineer starts their workflow in referential space, and what path they will end up traversing, is highly dependent on what they are doing and what they stumble across while they are working.
When customers are evaluating a product, what they need to understand is how the product solves some difficult problem for them, and this means the vendor must have a solid understanding of where their product fits in referential space. What difficult, error-prone, risk-heavy, or tedious path in this space are you solving? It’s important to know that even if you are solving a problem well, you are at the same time altering the landscape of this space. This is very important for the customer. This is what that drives them to want to understand the classic “packet-walkthrough”, for instance. If you are telling them “You won’t need to configure VLANs anymore” then you should be able to tangibly show them what they will be doing.
Ambiguity is bad. To the customer, ambiguity means an investment in time and and effort to understand and operate the product.
Coming out of the SDN hype-cycle, we have learned many things (I hope). The most important thing is that networking is really complicated. We can’t just make it go away. The most successful products have simply moved the complexity around, and they do this with little understanding of what network engineers do.
When vendors truly understand how user experience intersects with the complex space that network workflows happen in, then they can change how they build and deliver network products in innovative ways. The way to do this is by partnering with network engineers and their teams, and to really listen to how they work and the problems they actually have. Every part of the user experience should be tailored to make network engineers more effective.
In short, network engineers make better partners than they do targets. Understanding our customers means understanding networks in context. This is how we move networking forward.
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Feb. 28, 2017 01:15 AM EST Reads: 2,844
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
Feb. 27, 2017 10:30 PM EST Reads: 1,577
We call it DevOps but much of the time there’s a lot more discussion about the needs and concerns of developers than there is about other groups. There’s a focus on improved and less isolated developer workflows. There are many discussions around collaboration, continuous integration and delivery, issue tracking, source code control, code review, IDEs, and xPaaS – and all the tools that enable those things. Changes in developer practices may come up – such as developers taking ownership of code ...
Feb. 27, 2017 09:45 PM EST Reads: 3,055
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Feb. 27, 2017 07:45 PM EST Reads: 1,670
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
Feb. 27, 2017 06:45 PM EST Reads: 2,018
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed ...
Feb. 27, 2017 05:45 PM EST Reads: 795
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th 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 no time to wait for long developm...
Feb. 27, 2017 12:45 PM EST Reads: 2,159
SYS-CON Events announced today that Outlyer, a monitoring service for DevOps and operations teams, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Outlyer is a monitoring service for DevOps and Operations teams running Cloud, SaaS, Microservices and IoT deployments. Designed for today's dynamic environments that need beyond cloud-scale monitoring, we make monitoring effortless so you...
Feb. 27, 2017 11:45 AM EST Reads: 2,588
Cloud Expo, Inc. has announced today that Andi Mann and Aruna Ravichandran have been named Co-Chairs of @DevOpsSummit at Cloud Expo 2017. The @DevOpsSummit at Cloud Expo New York will take place on June 6-8, 2017, at the Javits Center in New York City, New York, and @DevOpsSummit at Cloud Expo Silicon Valley will take place Oct. 31-Nov. 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Feb. 27, 2017 11:30 AM EST Reads: 2,610
SYS-CON Events announced today that CA Technologies has been named “Platinum Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY, and the 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. CA Technologies helps customers succeed in a future where every business – from apparel to energy – is being rewritten by software. From ...
Feb. 27, 2017 11:15 AM EST Reads: 2,901
DevOps and microservices are permeating software engineering teams broadly, whether these teams are in pure software shops but happen to run a business, such Uber and Airbnb, or in companies that rely heavily on software to run more traditional business, such as financial firms or high-end manufacturers. Microservices and DevOps have created software development and therefore business speed and agility benefits, but they have also created problems; specifically, they have created software securi...
Feb. 27, 2017 11:00 AM EST Reads: 4,309
The emerging Internet of Everything creates tremendous new opportunities for customer engagement and business model innovation. However, enterprises must overcome a number of critical challenges to bring these new solutions to market. In his session at @ThingsExpo, Michael Martin, CTO/CIO at nfrastructure, outlined these key challenges and recommended approaches for overcoming them to achieve speed and agility in the design, development and implementation of Internet of Everything solutions with...
Feb. 27, 2017 10:00 AM EST Reads: 8,087
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his general session at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore...
Feb. 27, 2017 09:45 AM EST Reads: 1,942
This week's news brings us further reminders that if you're betting on cloud, you're headed in the right direction. The cloud is growing seven times faster than the rest of IT, according to IDC, with a 25% spending increase just from 2016 to 2017. SaaS still leads the pack, with an estimated two-thirds of public cloud spending going that way. Large enterprises, with more than 1,000 employees, are predicted to account for more than half of cloud spending and have the fastest annual growth rate.
Feb. 27, 2017 09:30 AM EST Reads: 1,264
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of Soli...
Feb. 27, 2017 09:15 AM EST Reads: 1,563
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" ...
Feb. 27, 2017 06:00 AM EST Reads: 6,238
After more than five years of DevOps, definitions are evolving, boundaries are expanding, ‘unicorns’ are no longer rare, enterprises are on board, and pundits are moving on. Can we now look at an evolution of DevOps? Should we? Is the foundation of DevOps ‘done’, or is there still too much left to do? What is mature, and what is still missing? What does the next 5 years of DevOps look like? In this Power Panel at DevOps Summit, moderated by DevOps Summit Conference Chair Andi Mann, panelists l...
Feb. 27, 2017 05:00 AM EST Reads: 7,512
When building DevOps or continuous delivery practices you can learn a great deal from others. What choices did they make, what practices did they put in place, and how did they connect the dots? At Sonatype, we pulled together a set of 21 reference architectures for folks building continuous delivery and DevOps practices using Docker. Why? After 3,000 DevOps professionals attended our webinar on "Continuous Integration using Docker" discussing just one reference architecture example, we recogn...
Feb. 27, 2017 04:00 AM EST Reads: 2,843
Hardware virtualization and cloud computing allowed us to increase resource utilization and increase our flexibility to respond to business demand. Docker Containers are the next quantum leap - Are they?! Databases always represented an additional set of challenges unique to running workloads requiring a maximum of I/O, network, CPU resources combined with data locality.
Feb. 27, 2017 03:00 AM EST Reads: 2,410
Thanks to Docker and the DevOps revolution, microservices have emerged as the new way to build and deploy applications — and there are plenty of great reasons to embrace the microservices trend. If you are going to adopt microservices, you also have to understand that microservice architectures have many moving parts. When it comes to incident management, this presents an important difference between microservices and monolithic architectures. More moving parts mean more complexity to monitor an...
Feb. 27, 2017 02:00 AM EST Reads: 1,910