On the Use of Online Containers for Development: ROI Review from Small to Large Teams

This is the recording of the conference talk at DevOpsPro 2023 in which Laurent Balmelli, CEO of Strong Network reviews the benefits of developing with Cloud Development Environments (CDEs). In particular, he discusses how security is critical for organizations using CDEs to manage their workforce.


Learn From an Industry Expert

Dr. Laurent Balmelli is co-founder and CEO of Strong Network. He sold his last cybersecurity start-up, Strong Codes to the US company Snapchat in 2016 and led cybersecurity efforts at Snap during a three-year earn out period from 2016 to 2020.

After earning his PhD from ETH in Switzerland in 2000, Laurent also worked 12 years at IBM Research Division and CTO office in New York and Tokyo before moving back to Switzerland.

Why Does It Matter?

This webinar is pivotal for contemporary enterprise development by highlighting the transformative role of Cloud Development Environments. Focused on collaboration, security, and efficiency, it reveals tangible advantages like a 50% reduction in development costs, accelerated release cycles, and heightened security postures.

It addresses pressing concerns of large teams, showcasing how Cloud Development Environments optimize workflows and deliver a substantial return on investment. The webinar provides actionable insights into optimizing infrastructure utilization, showcasing the potential to reduce costs substantially.

By leveraging Cloud Development Environments, development teams gain unparalleled visibility and observability, allowing them to measure and enhance various aspects of the development process. This efficiency is highlighted through real-time statistics, demonstrating the average build time and other key metrics.

What This Webinar Covers

Enhancing development efficiency: how cloud development Environments streamline development workflows, reducing time spent on planning, documentation, and dependency management.

Accelerating development life cycle and cost savings: how Cloud Development Environments save development costs exceeding 50% for companies through efficiency gains.

Securing development workspaces: how Cloud Development Environments enhance security by integrating Data Loss Prevention (DLP) measures, safeguarding sensitive data during development tasks and maintenance outsourcing.

Watch how Cloud Development Environments help you cut development costs!

Watch the recording of the conference on YouTube to learn how to use Online Containers for development.

Webinar Transcript:


All right, thanks a lot. I don’t think I’ve seen my charts so big before. This is me; sometimes, I shave my head, much to my wife's discontent, as she thinks I look like a prisoner. Nonetheless, it's fine, it grows back. I'm Laurent, I’m from Switzerland. I chatted with Vladimir because my partner and the company's city are in Serbia. We have offices in Belgrade and Lausanne, the French-speaking part of Switzerland, where I'm from.
Now, I want to explain the trend of putting containers online. While I assume there's no need to explain to anyone here the use and benefits of containers, I'd like to highlight a study quantifying the productivity benefits. As a coder or developer, using Docker on your laptop is going to make your life easier because you can isolate dependencies of your code and it's much easier to send some code to somebody else and say, can you try this? And you have all the dependencies and the things. So you have the whole infrastructure as code that you can send with the code itself. So everybody's aware of that, but there are not many studies that show what's going to be the business benefit of doing this. And I think if you're an organization, you might be willing to put some figures on that technology. So I found this study. And it’s publicly available, it’s from Forrester research conducted last year, I’ll give you the details.
What's new in this respected study is the focus on putting containers online. Because the study refers to the use of containers on your desktop, and on your laptop. So this is very common, but now that everybody's putting containers online, I know if you're not familiar with this, don't worry. I'll explain what this is. And I will give you examples of solutions. Then what is it, is there an additional benefit? And we expect this to be an additional benefit, but I want to explain it.

Background about myself and this talk

Just about myself, you can send me an invite on LinkedIn if you want, if you want to contact me about this talk. So my background is in cybersecurity. And that's why I build tools that somehow relate to cybersecurity. I'm interested in protecting data, especially in the case of a co-development process. You see something that I was just in a presentation before in security, the shift left. And I think, yeah, people are talking about, you know, securing all the tools that you use for back office and also the management of all the customer data and all these types of things.
But also there's an interest in protecting a development workforce because it's the largest attack surface that you have in organizations. A developer's laptop is actually a large attack surface and they're very sensitive to phishing attacks and malware. So I mentioned a few very recent interesting events that occurred earlier this year. And this is what interests me.
And also in this talk, I will introduce the way that online containers can also provide additional security and protection against that. My background in cybersecurity, and before we started Strong Network about two and a half years ago, we had a platform that I'll explain how it compares to other products that exist. But we're selling worldwide right now. And before that, I was working for Snapchat. You might be familiar with this if you have kids; I have two.
They’re currently into TikTok, for some reason. It surprises me that I still use Snapchat, and I have friends on Snapchat. It's not dead, right? I served as the Director of Cybersecurity for Snapchat. The reason I joined is detailed on my LinkedIn – they bought my previous startup, Strong Codes, a cybersecurity venture. There's no connection with our current project, Strong Network, but the acquisition led to the creation of Strong Codes.

The typical pain points for companies migrating to a DevOps process

My partner, co-founder and CEO, Ozrenko, and my partner from Serbia I mentioned before, worked with me at Snapchat. Now, providing context for my journey, I think it will be easier to understand. Now, consider transitioning to a DevOps process from an organization with a few years of development history. Without a robust DevOps culture, dealing with legacy tools and applications inefficiently deployed can be challenging. Companies aiming for a DevOps migration must address legacy tools and processes; managing outdated applications is both time-consuming and expensive to manage.
Lack of a DevOps culture is a common hurdle. As outlined in the DevOps handbook, the three principles, especially the principle of feedback, align with the modern approach to application development.

What are the expected benefits when moving to an agile methodology?

What is expected when moving towards an agile methodology, a precursor to DevOps, I'm not going to go through the history, but you know, you went to some steps before we called the steps up, but I think it started with The Agile Manifesto. And the benefit is to bring more team velocity, reduce development costs, exit releases, and so on.
Typically, when I was working for Snap, the interval between two releases, was about two weeks, we released a new application every two weeks. So it's very intense. You know, sometimes we're failing to release the application because the build was broken, but you know, I mean, I think about like 2000 developers were working on the app. You know, might be a surprise the first time you hear that, you say, oh, such an app, but it is so complex that we need that amount of developers working on it. So many things can break.
Team velocity, I also mentioned, like, there's also a lot of talk about how to measure team velocity, and this is something very interesting. Infrastructure efficiency, you want to improve asset utilization because obviously when you deploy your application, you have to do this as efficiently as possible because obviously when it's an operation, it costs you, right? This is especially important if your application is hosted on a cloud and not self-hosted, as hosting impacts the bottom line. Therefore, releasing applications in the most efficient way is vital, making asset utilization a very important concept in this context.
You want to make sure that your customers have an ROI that’s as high as possible. So you make sure that things are efficiently deployed. And operational risk reduction, this is something you can talk just about for hours, but you know, you want to improve developer experience but give collaboration between Dev and Ops team. Risk reduction is in many areas and I'll touch on some of them, but you want to make sure also that your process is secure and for instance, your source code is not stolen and that happens quite often.

The return on investment of using (offline) containers

Today, I'll explore the return on investment in four areas, based on the study I mentioned – "The Total Economic Impact of Red Hat Services and Support for OpenShift."
The study covers the entire container development and deployment process on Red Hat, providing end-to-end insights from development to production operations. I'll focus on four key areas that offer a glimpse into different stages across an application's lifecycle.
Firstly, the time required for developing, documenting, and designing an application. Can containers and good methodologies accelerate this process and foster innovation?
Secondly, application development testing and deployment cycles, a more familiar territory, are something we’re quite used to.
Thirdly, release cycles – efficiently updating and maintaining applications in production.
Lastly, the impact on production, the bottom line impact I mentioned before, specifically infrastructure utilization and the virtual machine footprint of the application.
The study involves companies with about 2,000 employees and 100 developers, providing valuable insights despite not being a large-scale enterprise. So this is not that much, right? Because it's not an SME, but it's not a large company. The company we work with, for instance, like their banks, to give you an idea, right? Because the first time I heard that, you know, my jaw dropped, like Bank of America, 60,000 developers. I don't know how they use them, but this is really what they have. And this is not uncommon.
Morgan Stanley companies have tens of thousands of developers. So it's amazing. So these are quite, you know, small companies do that, but it's not, it's not that small. It's not a startup company, right? So I think it's a good way also to assess because it's a good metric to create a study because you can kind of interpolate, you know, between and before. Larger companies, like banks, often have tens of thousands of developers, emphasizing the broad applicability of the study's findings beyond startups.
So I think it's a good way also to assess because I think you can, it's a good metric to create a study because you can kind of interpolate between and before. If the study was only made for 500 of 2,000 developers, people might take you with a grain of salt and say, ah, you know, it doesn't apply to us because we're too small, right?
So I encourage you to read that study and to see if you can learn something. Also, there were 150 apps, 50 new apps a year. So it's interesting. Three-year study period. So it's quite significant. The companies that were interviewed there, have limited development skills. So there's kind of a change of culture inside the company.
I think it's good information because you might not pretend that your company has all the skills for DevOps, right? You might have a few people who might be very good at this, aware of how to deploy efficiently to your process, especially on how you do this on the major clouds in terms of technology and all those things. But it's not something we should take for granted.

Containers can be used for DevOps both online and locally

Let's go. First of all, local versus online. So the study here, and this is one of my own, I read that study. I was like, ah, it's interesting because this is applying to the use of local containers. And, so just for a show of hands, like everybody who's not using Docker, who's using Docker, who's using Docker for containers? Yeah. And who's using online containers for development?
Okay. That's what I thought. So it's very common to use Docker on your laptop, but there's strength to it. So there are a few products that came out recently that allow you to use containers online. There's one called GitHub code spaces. Who has used GitHub code spaces before? So using online containers, but is that to try, right? Perhaps. Okay. Play around. Yeah. That's great. This is what people do.
There's also something called the Google Workstation. Does that ring a bell? It's very recent, right? I think it came out last year, and Google, they're not fantastic for marketing sometimes because they assume that everybody knows everything about them. So when they come up with a product, they don't even tell you, "Oh, there's new stuff coming up," right? So they don't spend a lot of money on marketing because they have a monopoly on many things.
Google Workstation is quite similar to code spaces with some different paradigms mentioned. Typically, a code space from Google is linked to the branch of your development, whereas a Google Workstation, as the name indicates, is like a workstation. It gives you, "Oh, I have this Linux machine that is online." It's like an EC2 instance on AWS but with different things and access to an IDE.
I'll show you something, but I'm glad people here in the audience are not very used to online containers. I can show you a demo. There's also a startup that came up with this a few years ago called Gitpod. Who knows Gitpod? Only a few people. I found more people who know Gitpod. There's another startup in the US called Coder. Have you heard about Coder? Okay, a few, even fewer people. So there are a few startups, and I think this is going to be more and more. Red Hat also has a service called, I hate the names, like DevEnv. It's really, I think it's really bad for marketing. Has anybody used DevEnv on Red Hat? No. Alright. I'm not surprised about that.
So what happened is that it's a trend that came about three years ago. It started two, or three years ago. The startups were like, it's great at that time. I'm sorry, about five years ago, but I think it was mostly unnoticed because there might not be a major adoption. And I'll tell you about what happened with our company. This is the logo for Strong Network. So personally, when I was, I had a three-year earn-out period with Snap, right? After three years, one day, I said goodbye and I wanted to create a new product. So I started looking around for what was in. This is actually when I looked at solutions like Gitpod and some of the things that I saw.
GitHub Codespaces was still better at this time. They came out like GA (Generally Available) last year, I think at the end of last year, maybe Q3 or Q4 last year. And I looked at this and thought, "Ah, this is interesting stuff, right?" But as a security guy, I was thinking, "Hey, can we add some kind of security to that?" So this is where we play a role, but let's first go into bringing containers online.

Let’s bring the use of online containers before the build stage

So what's the advantage of having online containers first? Since many of you today use Docker on your laptop, you know what to do, right? You create some code, do Docker build, Docker run, and so on. So it's, you know, you have to do all the manipulations yourself. But what you can do if you have online containers is going to be much simpler because basically, you can access your containers like there was a remote machine.
So I don't know if you know if you've lived through this time, but some time ago, Vladimir mentioned this yesterday, we're using SSH or even telnet. Who remembers telnet? Oh my, yeah. Right. So we might be the same age. So we were accessing remote machines and working on it. And you can do this today. You can spawn an EC2 instance, and then you can access, you know, with SSH and so on. So it's a bit like the same principle, but, you know, you're going to have a better way than just a text terminal to access the machine, but that's the thing.
So when you access the machine, actually what you're accessing is a container. It's a container that you can take as is and then bring to production. So you don't have to freeze you to do all this Docker build, Docker run, and all things. So that's what the advantages are, but then you need to have a good way to manage this. Let me show you what it looks like. I wanted to do a live demo, but you know how it goes every time you do a live demo, something fails. So I'm going to try to do so.
This is like a running container. I can see this is our platform. I'm not going to go through it. This is a bunch of running, this is all my team working on it. So we have, this is the Strong Network project. So we obviously developed Strong Network with Strong Network, you know, and you can have many projects. And so all these containers here, running containers are actually machines people are working on.
These are people in my team working partly in Switzerland and partly in Belgrade here. And I have my container here, my workspace, and then what I can do, I can open it. And this is Visual Studio Code running. This is, look at this, this is running on my laptop. So it's running on my browser as a web application, but here I'm connected to a container. So here, if I physically create a file, this file was created remotely on a running container and Kubernetes in AWS.
So it's actually not living; this is a Chromebook. So it's not really living on my machine. If you remember the SSH stuff, this is a principle: you create something remote, and it doesn't exist on your machine, right? So here you're really living in a Linux container. And this is something that you can bring straight into production here. So this is it. And let me just... yeah, so this is your stuff. Basically, I can also open that thing here as a terminal, because if I like VI terminals, it's a file I was doing before, and I can use Vim and so on.
And this is... so I can actually access my container in different ways, but this is everything happening here in the browser. What's the advantage of doing this? I think it's a bit like Google Docs, right? You can open your complete environment for development anywhere on any machine, right? You don't have to reinstall things.
So basically, it becomes like the hardware and stuff becomes not your main concern when you're working, because here, everything that happens, even the compilation of the code, will happen on the cloud. So using a machine that is running in the cloud, you compile your thinking, and what you have on your machine here is just a display.
And if you've been tortured by using a remote desktop for development or Citrix VDI, I obviously don't think this is the same, because this is not streaming the desktop, right? This is something that is completely executed. So it's the same, and it's a hundred percent the same code of VS Code that is running, that can actually be installed locally because I think the version of the VS Code is actually running in a mini browser. The one installed locally is running a mini browser. It's actually written in TypeScript and it can run efficiently like that.
So that's the thing. And you can see how many workspaces and so on. If I want to create a new workspace as a developer if I want basically, I mentioned this, to onboard somebody, I can actually create this thing. I'm just going to create one more here for the demo. This one, I'm going to create one for data science here. I can take an image. So basically here, my resources, I'm going to... This is where I select my container. I selected the container here. I think it's big enough. Yeah, it's big enough.
I selected my container here. I can share this with somebody else. I'll show you the sharing effect. I can select the ID. I have VS Code, I have some PyCharm, like Intel from Jetplane, and so on. I can select the number of CPUs and so on. I'm going to select the resource I want to access here. I can access an entire application.
But what I'm going to do here, I'm going to access like a special project that gave me some, some Jupyter notebook. So you can do coding or science. It doesn't make any difference to me, I think. I'm not going to go into the security thing, but I'm going to put a bit of monitoring on what's happening on my workspace because I'm going to share some, you know, personal, like, diabetes information. So I don't want this to be different.
So basically, I want to protect this against exfiltration. And here, I will deploy my workspace and so on. And I can actually... I will have this ready in a few seconds. Let me go back to things. So this is what it looks like. Once you can actually manage containers online, you know, everybody's going to access this UI.
And, people that have ownership of workspaces, will see workspaces coming up here. Since I'm a project owner, I will see all the workspaces in my team here. Here, for instance, you can see this one is shared with me. So I just want to show you what happens in some... see this moment is running now. I'll go back to it. But for instance, Bjorn here was one of my employees. He has shared his workspace with me so I can open his workspace here. And it's like, again, like we would share a Google Doc.
I can go and say, "Let me help you with this." And you can see I'm connected because, you want to maintain privacy, you can see I'm connected to his workspace here. So this is, and we can have any number of people, right? And you can say, like, you know, "Cool, it's called peer editing, or peer coding." Have you heard about peer coding before?
So this is something that is fully supported here. And you can do this with any number of people. I would not advise doing this with a lot of people because it might be a bit messy. But this is something that we can do. There you go. So let me just go back and go on the results of the study.

Platforms that offer online containers for development

Now that we know what's happening, just one thing. I mentioned there are many solutions for online containers. I mentioned GitHub code spaces, Google Workstation, Gitpod, Quarters, and StackBlitz – sorry, there's a typo here – CodeSphere.
But I mean, all these types of things. And here, this is our platform, the difference with our platform and other things that I'm not here to talk about our platform in particular, is that we actually added all enterprise data protection.
So here's what we do, basically what you would do by deploying a Citrix VDI, VMware Ryzen, AWS WorkSpaces, and DevBox, in terms of data loss prevention, we'll do it but with containers. So that's how we position ourselves. That's why actually, we actually work with the banks, the insurance, and companies that need this kind of protection.

Benefits around application planning, design, and documentation

The first result I want to talk about is that using containers locally reduces the time you have to plan, document, and design expectations by over 80%. So that's the first result. And I think it's interesting to see because over 80% might sound really interesting.
But if you look at the results, if you look at the number of applications that can be built annually, this is where you get this type of metrics, right? Because what they did to get that type of information is like, see, how many applications can we build per year? And again, I don't know about your organization, but they have 50 new applications per year. Since a lot. But I guarantee you, when you work with banks, it's normal.
So that's one of the interesting things here is that it's actually not crazy numbers, but this is the thing. Basically, here you can see that one way to release more applications is to when the things are containerized, it's much easier because you would deal less with issues related to planning, documentation, and dependencies. One of the advantages is that what I was mentioning is that if you want to be efficient here, you have to have a way to manage your containers efficiently.
This is where basically, in a platform, you need to look for an efficient way to manage containers. So I'll show you this here that is very easy to, you know, go and access your containers, you can see all your workspaces, you can, so if you have a way for your employees to quickly access containers and create a new container, I did that just before. I created the one for DataSense here that I did, and you can see here that in a few seconds actually I created a new container.
Look at this, this is an interesting thing: now the project that I connected here is an authenticated project. It's not public, it's not a private repo, it's actually a private repo, but it's already completely cloned and all the keys, everything was done for you. So this is one of the big advantages when you have online containers, there are many operations that the developers would have to do that they don't need to do anymore because we actually can manage all the security for them.
So the big advantage is that, well, first of all, none of the keys here would live really on the workspace, they would live somewhere in the proxy. This is the differentiator that we have with other online containers, right? All the keys will be, so we basically free developers from managing any of these credentials and so on.
If I want to start working, then if you're a coder like me, you know, SSH keygen, you have to get your private key, put your public key into the repo, and then cloning is going to take you half an hour and it's annoying. So here everything is already done, and look at this, it's fully configured because the container that I used here from my workspace is completely configured, it's completely configured for the usage of data science in this case, so all the libraries that you have to install here.
And if I try to run an application because that's also a common question that people have, since I'm already online, how can I run an application on a local host? How can I run an application that, you know, because it's already online, this kind of inception-type of recursion, right? But you can do that here because we actually support that stuff.
So I'm going to run an application, this little application called Voila that runs an application here. So with support here, we can create an app automatically. This is an extension that we built for VS Code. I'm going to create an app here. I'm going to make it public, I'll spin that to UI, and here I have an app running data science, and what's going to happen here is that when I go back to my UI, the app I'm running here appears here automatically, okay?
And I can open it and voila, and this is my app running. So this is running on my workspace and so on. Something cool for collaboration is that, let's say now I take this URL and put it in there. Let me just put it here. There you go.
And if you scan this, you can open this application on your phone. It's running on my workspace, you can scan this, and you'll be able to open this application right in your browser. So, to collaborate, because I made the link public, I can send this application to anybody in the world. So if I want somebody to check my UI and so on, you can actually open it. If it doesn't work, let me know, but normally it should be working.
So we're good? Okay, it's working. Okay, thank you. So I can actually send you that application. In terms of collaboration, it's really cool, right? Because you can do really amazing things with that. In terms of access, this is really resource creation management. This is really something that can help you.

Benefits around application upgrade, maintenance, and management

And that brings us to a second result here. It lets you accelerate application development and testing, right? And in this case, it showed that you can slash costs by more than 60%. I'm not going to go into all the details. What happens when you do this online? Then, this is what I was explaining before, is that once you have an online container, here is what I did before when I opened this with VS Code here, I'll actually have what is called a cloud IDE, right? This is the way to run VS Code on the browser. But you don't have to do this necessarily.
You can also open it here, at least on our platform, you can open this, you can access this container with SSH. It's an extension of VS Code that is called VS Code Remote Dev, or something called JetBand Gateway.
And you can actually connect to your container using the local IDE. So you're not forced to use the cloud IDE. If you don't want to, you can also connect with a local IDE. In terms of connection, it's really good. But like, what we can do more than that is you can actually manage all the credentials, all authentication to this. So basically, your developer doesn't need to deal with credentials anymore.
And we're not only talking about credentials for Git, but also credentials for any type of resources like HTTP, SSH, and stuff. And what we do here also is on the platform, we actually give access directly to GitHub to the platform here. And you can basically access your GitHub directly from here. And this is going to be through a secure browser here. Yeah, just gonna go for the interest of time. There you go.
All right. Okay, the third result here is that developers accelerated release cycles and application update and maintenance costs by 50% on average. There's something here that's very important because what happens in many companies is that maintenance and upgrade of applications are sometimes not done by the original developer team.
It's actually a lot of the time that maintenance applications are outsourced. It could be more efficient in countries where labor costs are lower. However, we're not going into detail about that. What happens here is that this is where security becomes very interesting because many companies, when they outsource the maintenance of applications to remote development teams, may face issues with data, source code, and so on. Strong Network played a role in securing these types of relationships by offering a solution that provides security.
Typically, outsourcing maintenance was done with VDI, Citrix, remote desktops, or even tools like TeamViewer. So I don't know if you try to code through TeamViewer, it's a nightmare, right? But, you know, it's like a poor man. And actually, it doesn't even protect you because the clipboards can still be, you know, copied and everything.

The maintenance and upgrade of applications is also an external affair

So what we do here is that I think DLP really creates a lot of value for that. However, these methods often lacked proper security measures. With solutions like Strong Network, Data Loss Prevention (DLP) plays a significant role in securing these relationships. And what I want to show you here is that even large companies, you know, they actually get hacked. And they'd have no protection if there's not something that is put in place.

Recent credential exfiltration SNAFUs

So if you're interested in security, I wrote that article a few months ago here that explains basically how that was. I think January or February, Slack, Okta, and CircleCI got all hacked from their source code. Why? Because they are credentialed all over the developer's laptop, right? And, you know, if there's nothing done for that, then basically, you know, simple phishing attacks, which is exactly what happened to them here.
A phishing attack basically will, you know, make, you know, your source code open source for everybody, right? Which, you know, if when you Okta, it's an issue, right? And or Slack or like like it's also one password, I think they have the main issue. So password manager's source code is becoming open source, it's an issue, right? So here.

Infrastructure utilization efficiency savings on operations

And the last one I wanted to mention here before, I was hoping to leave a bit of time for a question, and I can show you more things about the demo, is the efficiency of infrastructure utilization, right? I think this is something that's very important because I mentioned that at the beginning, this is really your bottom line cost. This is what much is going to cost you to run the application here.
So basically, obviously, using containers, you don't necessarily deploy directly containers, you can do, you know, efficient twist like a Lambda function, or you can run serverless and this type of thing. But, you know, it's basically a far cry compared to what you would do if you deploy directly VMs and so on. So, especially when you have also microservices, you can improve the asset utilization. And this is something that, you know, we reduce your cost or your cost of your customers in case you're selling self-hosted applications.

The (virtual) secure developer laptop

One thing also I wanted to mention here is an article that I wrote about the whole concept that the developer laptop is getting virtualized.
So this is in effect what's happening with online containers, right? Because when you have online containers, is that your, I mentioned before, is that your laptop is interchangeable from the hardware perspective, right? I can use, I can use this laptop to code, but if I go home, and I open up and I can open my environment, and I have the same thing, I don't have to reinstall anything.
This is one of the, you know, the huge benefits of having a thing that runs basically online is that you know, I can open like any number of different projects, and things will be, you know, running from this Chromebook or my Windows machine or my Mac at home, and so on. I don't have any issue with this.
This is one of the advantages, and this is why, the advantage of having online containers, it is basically the orientation that we took as a company, as Strong Network, not only do you make your development portable, you make security portable. We want the security to follow the developer, right?
So basically we don't want to have any information that could be used to hack the company on the laptop. So even if you use a laptop, it doesn't matter. It's not, it's not basically an issue for the company. And if you look at this article, if you read what I did in this article to explain a bit of the history of that, because if you look at what happened, like in the last 10 years, the first data that went from the developer's lab to the cloud was customer data, CRM data.
Before Salesforce, many salespeople were traveling with the entire customer data on the laptop. So it was a catastrophe, basically, when they lose a laptop or something like that, because it exposes the company to litigation, like regulations and all those things, right? So I think this is one of the main issues.
This article explained the different steps of evolution, and now we're getting to the last type of data that is really living on some of, actually perhaps most of the developers' laptops, which is the source code and data and credentials that access your online application, right? And this is really what is moving now to the cloud. Actually, this is exactly the reason for all these new Google workstations, GitHub code spaces, applications like ours, and some other stuff.
This is really why this is happening. So this is kind of the last step in the evolution of the thing. Yeah, oh yeah. This is because I want to show you, that one of the really cool stuff that happens with putting a container online is visibility. So there was a really interesting talk yesterday about observability and how you can bring information back to your development.
So here we have what we call insights. So what we call insights, basically we have a CLI. We can actually make any type of measurement we want on the entire workforce in their workspaces. So here, for instance, I can measure, this in real-time data, this is basically the average build time of my developer.
So whenever they build, automatically I take the result and I put it in the back end, I do statistics, and I report it here. So in real time, the project manager can look at what's the average build time. And you know, you can see, oh it's getting up, you know, it's getting down. So this is something that is really valuable information, which is actually impossible to read if you don't have online containers.
Once you have online containers, you have a huge benefit in observability and so on. So you can measure pretty much everything you want. And you know, so we do this for processes, you know, resource allocation also. We know basically how much the Kubernetes cluster is going up and down in terms of process allocation and so on.
So you can control your costs and all those things. And interesting, we did a lot of TCOs, total cost of ownership study. Actually, it's much cheaper than laptops. Again, it's actually half of the cost. If you manage your entire team with online containers and a $1,000 Chromebook, which is quite a cool Chromebook, then it's actually half the price you will use for your laptop. Your normally developed laptops, we're talking about like Macs and several things.
And for the same, basically, power, because you know, they have access to the cloud and if they want a 128 CPU machine, they can have it for a few hours. For you, it will be like an incremental expense. So there's also a user benefit, also sustainability, right? Because we don't need to consume that much like experts in hardware and something that is also... This is actually one of the aspects, also it's very interesting to explore.
And I'm also getting to the end of this talk because if you... I have a whole series of webinars that I'm giving on these things, like for instance replacing the use of secure laptops for developers, regulatory and security compliance, and so on here. So if you want to... I actually have one on June 1st.
On June 1st, I'm going to talk about DevSecOps automation and governance. So I use it because there are a lot of things you can do on DevSecOps with online containers that could be fully automated. So it's an efficient thing. So if you want to attend one of these webinars, please feel free to scan this code.
And then again, please contact me if you have any questions. That's it.
All material in this text can be shared and cited with appropriate credits. For more information about our platform, please contact us at hello@strong.network
Copyright © 2020-2024 Strong Network All rights reserved.

Coding Productivity Meets
Enterprise Security

Interested to learn how Strong Network is solving problems of some of the world’s biggest Enterprises?
Book a Demo with one of our experts today!