10 minute read

WebAssembly finds second home in the cloud

Next Article
News Watch

News Watch

Play-Doh may be a favorite toy from your past, but its creators never set out with the goal of making a toy. It was originally marketed as a tool for cleaning your wallpaper before it found its way into the toy aisle.

Many other inventions started off aiming to solve one problem only to find themselves becoming known for an entirely different use case. And WebAssembly, or wasm, may be on a similar path.

WebAssembly is a bytecode format that code can compile to and it enables different programming languages to run in the browser, explained Liam Randall, CEO of Cosmonic, which is a WebAssembly PaaS.

“WebAssembly has huge implications for the web platform — it provides a way to run code written in multiple languages on the web at near native speed, with client apps running on the web that previously couldn ’t have done so, ” the Mozilla WebAssembly documentation states.

Beyond the browser, people have been using it with great success in the cloud, containers, and the edge.

WebAssembly is polyglot, portable, and interoperable. Because of these capabilities, developers can pick and choose from applications written in a variety of languages.

“Just like an electrical outlet, which enables you to turn on a light without knowing where the power comes from, contracts will deliver what they say they ’ll deliver. Look for GitHub to be used to distribute libraries as WebAssembly LEGO, where developers select contracts to pull and maintain large pieces of code that can run in any cloud, and any edge environment, ” said Randall.

This LEGO concept works also to enable contributions from users. For example, there are many places where someone might want to add something to an existing application as a plugin. A company like Shopify or a game like Microsoft Flight Simulator might want to allow users to submit code to customize their experience. According to Randall, this is exactly what people are doing with WebAssembly.

Randall believes that in cloud environments WebAssembly can be really powerful because most of today ’ s business logic is on the server side, running in public clouds and in data centers.

“The ability for us to put applications that run or to create applications that can seamlessly run anywhere across that spectrum, is really powerful, ” Randall explained.

BY JENNA SARGENT BARRON

Adobe’s WebAssembly success story

For example, Adobe Photoshop ’ s codebase was started in the ’80s, but it was able to be recompiled to run right in the web browser using WebAssembly.

“As Wasm has standardized with features such as threads, and developer tooling for Wasm has improved, we have continued this journey to the web, culminating in our new web-based Photoshop experience. Wasm allows us to keep the same core C++ code base — compiled to the desktop, mobile and browser, ” Sean Isom, engineering manager at Adobe, and Colin Murphy, senior engineer at Adobe, wrote in a blog post.

Isom was on a mission to improve the efficiency and performance of the company ’ s infrastructure, while lowering costs. The company runs 90% of its containers in Kubernetes, and recently he shared details about how they were able to combine Kubernetes with WebAssembly.

Some of the use cases Adobe has achieved includes running existing functions in wasmCloud and running wasmCloud as a service in Kubernetes clusters.

WasmCloud is an open-source project for building distributed applications using WebAssembly that is currently housed under the Cloud Native Computing Foundation as a sandbox project. The project was a big focus at this

year ’ s KubeCon NA, where Cloud Native Wasm Day took place to offer up sessions on using WebAssembly in cloud-native use cases.

“I love WebAssembly, ” Isom told SD Times in an interview. “It’ s been a large lift and shift initially to get stuff working in this, but I have been working on developer experience tooling for years now. And I’ ve seen us come so far in the past year, even just in the last few months, it’ s becoming easier and easier. And I’ m really excited to get this over the hump where it’ s going to be a really repeatable thing that lots and lots and lots of the services that the teams can use in the coming years. ”

WebAssembly causing quite the disruption in the ecosystem

Randall said that it is on the app platform side where WebAssembly is “ poised to make the biggest disruption ” because it is so small and fast. Containers, even highly optimized ones, can take a few seconds to start up, while WebAssembly offers applications a cold start time of less than a millisecond.

“When we think about how logically containers really powered this great lift and shift into the cloud, but WebAssembly is poised to enable the buildout of complex capabilities across the distributed ecosystem of today, ” Randall said.

In fact, in 2019 when the WebAssembly system interface WASI was announced, Docker creator Solomon Hykes tweeted: “If WASM+WASI existed in 2008, we wouldn ’t have needed to have created Docker. That’ s how important it is. WebAssembly on the server is the future of computing. ” z

BY JENNA SARGENT BARRON

In 2019, most business leaders probably wouldn ’t have predicted the changes that would be coming their way in early 2020 thanks to a global pandemic. If they had, perhaps they would have been able to make decisions more proactively and wouldn ’t have had to scramble to convert their workforce to remote, digitize all their experiences, and deal with an economic downturn.

Now, the country is in another period of uncertainty. You ’ ve read the headlines all year: The Great Resignation, layoffs, a possible recession, Elon Musk’ s takeover of Twitter shaking up marketing spending, introductions of things like GitHub Copilot and ChatGPT having workers worrying about their future job security, and more. The list could go on and on, but one thing that would help people through these times is knowing they ’ll make it out okay on the other end.

Unfortunately that level of predictability isn ’t always possible in the real world, but in the business world, value stream management can help you with it.

According to Lance Knight, president and COO of ConnectALL, the information you can get from value stream management can help you with predictability. This includes things like understanding how information flows and how you get work done.

“You can ’t really be predictable until you understand how things are getting done, ” said Knight.

He also claimed that predictability is a more important outcome of value stream management than the actual delivery of value, simply because of the fact that “ you can ’t deliver value unless you have a predictable system. ”

Derek Holt, general manager of Intelligent DevOps at Digital.ai, agreed, adding “If we can democratize the data internally, we can not only get a better view, but we can start to use things like machine learning to predict the future. Like, how do we not just show flow metrics, but how do we find areas for flow acceleration? Not just what are our quality metrics, but how do we drive quality improvement? A big one we ’ re seeing right now is predicting risk and changing risk. How do you predict that before it happens?”

Knight also said that a value stream is only as effective as the information that you feed into it, so you really need to amplify feedback loops, remove non-value-added activities and add automation. Then once your value stream is optimized, you can realize the benefit of predictability.

If you ’ ve already been working with value streams for a while then it may be time to make sure all those pieces are run-

< continued from page 21 ning smoothly and look for areas where there is waste that can be removed.

Knight also explained the importance of embracing the “holistic part” in value stream management. What he means by this is not just thinking about metrics, but thinking about how you can train people to understand Lean principles so that they can understand how the way they develop software will meet their digital transformation needs.

Challenges companies face

Of course, all that is easier said than done. There are still challenges that companies face after adopting value stream management to actually get to the maturity level where they gain that predictability.

One issue is that there is confusion in the market caused by vendors about what value stream management actually is. “Some people think value stream management is the automation of your DevOps pipeline. Some people think value stream management is the metrics that I get. And there ’ s confusion between value management and value

continued on page 25 >

What sets successful value stream management practices apart

Chris Condo, principal analyst at Forrester, last month wrote a blog post where he laid out the three qualities that set successful value stream management practitioners apart.

1. Use of AI/ML to predict end dates. According to Condo, development teams with access to predictive capabilities are able to use them to create timelines that are more likely to be met. He noted that the successful teams don’t replace estimates produced by people on their team, but rather augment those estimates with machine estimation.

2. Bottleneck analysis. Teams can use value stream management to discover what the real cause of their bottlenecks is. “When it comes to VSM, too many clients put the cart before the horse, thinking that they need a high-performing DevOps culture and tool chain to effectively use VSM. None of this could be further from the truth, ” said Condo.

3. Strong metrics and KPIs. Development leaders want these metrics if they are going to be putting money into value stream management, so look for vendors that can provide excellent metrics. z

An interview with Lance Knight, president and COO of ConnectALL

< continued from page 22 stream management, ” said Knight.

Knight wants us to remember that value stream management isn ’t anything new; It can trace its origins back to Lean Manufacturing created by Toyota in the 1950s in Japan.

And ultimately, value is just the delivery of goods and services. Putting any other definition on it is just the industry being confused, Knight believes.

“So people who are trying to implement value streams are getting mixed messages, and that’ s the number one challenge with value stream management, ” said Knight.

Digital.ai’ s Holt explained that another challenge, especially for those just getting started, is getting overwhelmed.

“Don

’t be paralyzed by how big it seems,

” said Holt. He recommends companies have early conversations acknowledging that they might get things wrong, and just get started.

Where has value stream been? Where is it headed?

In our last Buyer’s Guide on value

KEY TAKEAWAYS

1. Predictability is the key outcome for value stream management

2. Value stream management is a continuous process of improvement

3. Metrics are key to prove that value stream management is adding value

stream management, the theme was that it aligns business and IT.

Holt has seen in the past year that companies are adopting mentalities that are less about that alignment. Now the focus is that software is the business and the business is software.

In this new mentality, metrics have become crucial, so it’ s important to have a value stream management system in place that actually enables you to track certain metrics.

“Things like OKRs continued to kind of explode as a simple means to drive better outcome-based alignment … simple KPIs around objective-based

development efforts or outcome-based development efforts, ” said Holt. Holt also noted that in Digital.ai’ s recently published 16th annual State of Agile report, around 40% of respondents had adopted one of these approaches, and that was significantly up from the previous year. He went on to explain that companies investing in value stream management want to be sure that their investments are actually paying off, especially in the current economic climate. He also said value streams can help organizations make small, evolutionary improvements, rather than one big revolution. “Value stream management is building on some of the core transformations that happened before, ” said Holt. “Wiithout the Agile transformation, there would have been no DevOps, and without Agile and DevOps, there probably wouldn ’t be an ability to talk about value stream management. ” So value stream management will continue to build on the successes of the past, while also layering in new trends like low code, explained Holt. z An interview with Derek Holt, general manager of Intelligent DevOps at Digital.ai

This article is from: