Welcome!

Java IoT Authors: Stackify Blog, Yeshim Deniz, Pat Romanski, Matt Lonstine, Glenda Sims

Related Topics: @DevOpsSummit, Containers Expo Blog, @CloudExpo

@DevOpsSummit: Article

Rapidly Evolving DevOps Tools By @OmniTI | @DevOpsSummit [#DevOps]

DevOps is all about removing barriers to rapid, safe delivery of new experiences to your customers

Four Ways to Manage Rapidly Evolving DevOps Tools

We all want rapid innovation, but we don't want to have to integrate with it every day.

What Is a DevOps Toolset?
DevOps is all about removing barriers to rapid, safe delivery of new experiences to your customers. Much of this revolves around automating error-prone, human-driven processes so that processes can be standardized, scaled, and varied programmatically. Some of the types of tools used in a DevOps-minded organization might include version control systems, automation servers, and configuration management systems. Many tools can be used across categories, with varying amounts of success. Some vendors offer products that claim to address all of these needs with one solution - most rarely deliver on that promise.

The Pain
Automation is not helpful if each stage of the software delivery and operation cycle automation is isolated. Steps need to flow continuously, with each tool integrating into the overall picture: your CI server needs to talk to your version control system, and probably your IaaS system (for ephemeral test environments). The IaaS system has to talk to the monitoring system, to ensure new nodes are monitored and decommissioned nodes are not flagged as down. And everything has to talk to the communications layer, but not fill the channel with noise.

This is a huge integration job, especially as each piece is changing rapidly. As the DevOps landscape evolves, it can be very hard to get stability in your architecture.

Approach: Stop Time
One approach is to simply adopt a current version of a tool and commit to using it. Instead of dealing with upgrades and tool changes, your team's time will now be focused on delivering features. This may sound appealing as it is much easier to certify a toolset for security, and to fully operationalize it if it does not change. Each toolset change requires changes in run books and training, so fewer changes means less team-impacting shifts.

Unfortunately, this approach is typically not practical for more than a brief period of time (perhaps a year). For example, any new features or bug fixes for the tool will not be available to the team and, worse, as tools come in and out of favor, you may find yourself using a tool that no longer has community support or documentation, or reached an end-of-life. In addition, if one of the tools is a SaaS (which is increasingly likely), you may find that the provider dropped support for your desired version of the API, or shifted its product line to an entirely new API structure.

More subtly, the implementation of the tools may make it very difficult to freeze time. For example, many tools have cross-dependencies on libraries that result in forced upgrades when you upgrade one component. While this is tedious on a day-to-day basis, it can be disastrous if left unmanaged for long periods of time - you may find yourself wanting to upgrade one piece due to a security issue, but forced to upgrade several pieces because of overtight version dependencies. It may even force you to swap out a tool that is no longer actively developed and supported. Each dependency change can have a snowball effect and the longer the time interval between updates, the more likely it will become an avalanche.

Approach: Try to Keep Up
On the opposite end of the spectrum from stopping time, some shops choose to constantly stay on the bleeding edge of the tooling space and adopt tools, versions and workflows as they become available. Typically, passionate individuals will follow a particular project closely, which can translate to expertise within the team and excellent support for the tool.

More commonly, however, individual passion does not translate directly into organizational success. Not all groups will have the same tolerance for instability and integration rework, so it's easy for this approach to become divisive and increase friction among teams. Enthusiasm for the tool may wane, or the passionate individual may be re-assigned or leave the company. Even if support for a tool is broad, staying on top of the latest changes will always require much effort and tradeoffs: the tools that integrate with the new tool may not yet support the new features.

One compromise that often works well is to have a "skunk works," or R&D group, that experiments with new techniques, then sees them through to adoption once they are stable and integrated with the rest of the toolchain in use. It is important to brand this group as a tooling team, not a "DevOps Team."

Approach: Outsourcing
Whenever you're faced with a large integration project across several closely related tools, consider looking to a major vendor for an integrated approach. For example, using a combination of AWS offerings, you can construct a working, nearly complete DevOps toolchain that you can be assured will work well together. By spending more on professional services, you can also have Amazon build out any missing pieces of integration to ensure you have a smooth flow. Other vendors provide similar offerings.

Vendor lock-in is a major drawback here. It will be very difficult, if not prohibitive, to switch providers at a later date: the APIs, tool features, and capabilities will be similar but different enough to invalidate all integration efforts to date. Additionally, outsourcing the entire toolchain will not be cheap, and the ever-evolving nature of the tools means that the custom development cost will never go away - the integration work will never be "done."

Most perniciously, however, is that by hiring people outside your organization to make your DevOps toolchain, you explicitly push outside the lessons learned by having developers and operations staff work side by side to solve each other's' problems. When people share their problems, they tend to come up with solutions quickly. But if a vendor is providing the interface, tooling, and support, you have a big wall between the people who encounter a new problem and the people who are remedying it. That is antithetical to the DevOps approach, and your team will not magically "become DevOps-y" if they don't actually solve problems together.

Approach: Make a Local Wrapper API
Increasingly the underlying components of the toolchain are being offered as services with an API in front of it. In some cases the service is run on-premises, in others they are SaaS; but either way, the coupling is much looser. This allows you to write your own API end points, which perform the tasks your internal customers need to perform, while calling out to the various back-end tools and services. Users need not know which components are actually tools (possibly with awful dependencies) and which are services; in some cases, you may also choose to hide provider-specific details, such as which cloud provider was used to provision a node. Passionate individuals may work on the internal API layer, adapting it to the latest version when new features are desirable. This can usually be done while still providing a stable, backwards-compatible API to the internal customer. The local wrapper API is also an ideal location for various bits of integration (like security checks, inventory management, etc.).

Locally developed APIs are not without their drawbacks. Each internal customer has to agree to use it; the documentation and support must be excellent, and the value compelling or people will revert to simply using the various tools directly. That may not be a problem, especially for groups with unusual needs. Interface levelling - in which unique features of a provider are masked in favor of broader commonalities - can often be more of a problem; in some cases, it may make sense for a user needing Azure-specific features to have an Azure-specific part of the API, for example. Finally, it can easily turn into "one API to rule them all" in which scope creep forces the pull of more and more services under the same roof that was not designed to accommodate the diversity.

That highlights an important aspect of the local wrapper API: when internal customers have unmet needs, they can reach out internally to the API developers and operators - which, in fact, may be the same people.

Conclusion
There is no obvious, simple way forward when dealing with rapidly changing toolsets. Each approach has serious drawbacks, but some compelling advantages. Most organizations will end up using a mixture of approaches - perhaps "stopping time" with automation tools like Chef, but staying bleeding edge by leveraging latest features from a platform like AWS, and a custom local API gluing together their monitoring, communications and inventory control systems. Approaches will vary from group to group as well. As with anything in DevOps, the goal is not some ideal destination as implemented at a unicorn company, but rather gradual, continuous improvement to the processes that most impact your ability to deliver and operate quality software quickly.

More Stories By Clinton Wolfe

Clinton Wolfe leads the DevOps Practice at OmniTI and has been helping organizations deploy and operate web-scale applications since early days of the web. He is especially versed in testable infrastructure, the people problems of highly constrained workplaces, and aligning business needs with engineering capabilities. He collects metrics for fun.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that Conference Guru has been named “Media Sponsor” of the 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. A valuable conference experience generates new contacts, sales leads, potential strategic partners and potential investors; helps gather competitive intelligence and even provides inspiration for new products and services. Conference Guru works with conference organizers to pass great deals to gre...
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and shared the must-have mindsets for removing complexity from the develop...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
"Evatronix provides design services to companies that need to integrate the IoT technology in their products but they don't necessarily have the expertise, knowledge and design team to do so," explained Adam Morawiec, VP of Business Development at Evatronix, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices to ...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
Large industrial manufacturing organizations are adopting the agile principles of cloud software companies. The industrial manufacturing development process has not scaled over time. Now that design CAD teams are geographically distributed, centralizing their work is key. With large multi-gigabyte projects, outdated tools have stifled industrial team agility, time-to-market milestones, and impacted P&L stakeholders.
"Akvelon is a software development company and we also provide consultancy services to folks who are looking to scale or accelerate their engineering roadmaps," explained Jeremiah Mothersell, Marketing Manager at Akvelon, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"IBM is really all in on blockchain. We take a look at sort of the history of blockchain ledger technologies. It started out with bitcoin, Ethereum, and IBM evaluated these particular blockchain technologies and found they were anonymous and permissionless and that many companies were looking for permissioned blockchain," stated René Bostic, Technical VP of the IBM Cloud Unit in North America, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventi...
In his session at 21st Cloud Expo, Carl J. Levine, Senior Technical Evangelist for NS1, will objectively discuss how DNS is used to solve Digital Transformation challenges in large SaaS applications, CDNs, AdTech platforms, and other demanding use cases. Carl J. Levine is the Senior Technical Evangelist for NS1. A veteran of the Internet Infrastructure space, he has over a decade of experience with startups, networking protocols and Internet infrastructure, combined with the unique ability to it...
22nd International Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, and co-located with the 1st DXWorld Expo will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud ...
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
Gemini is Yahoo’s native and search advertising platform. To ensure the quality of a complex distributed system that spans multiple products and components and across various desktop websites and mobile app and web experiences – both Yahoo owned and operated and third-party syndication (supply), with complex interaction with more than a billion users and numerous advertisers globally (demand) – it becomes imperative to automate a set of end-to-end tests 24x7 to detect bugs and regression. In th...
"MobiDev is a software development company and we do complex, custom software development for everybody from entrepreneurs to large enterprises," explained Alan Winters, U.S. Head of Business Development at MobiDev, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, discussed how from store operations and ...
"There's plenty of bandwidth out there but it's never in the right place. So what Cedexis does is uses data to work out the best pathways to get data from the origin to the person who wants to get it," explained Simon Jones, Evangelist and Head of Marketing at Cedexis, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
SYS-CON Events announced today that Telecom Reseller has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Telecom Reseller reports on Unified Communications, UCaaS, BPaaS for enterprise and SMBs. They report extensively on both customer premises based solutions such as IP-PBX as well as cloud based and hosted platforms.