[MUSIC PLAYING] Welcome ladies and gentlemen to Build an Office. Today we are talking again about One Identity, One Identity Manager. And today we decided to talk about containerization in One Identity, categorization in One Identity Manager.
Because of that, I have two experts on the desk. One expert for Product Identity Manager. It's Alex Binotto, Senior Program Manager for our product.
On the other hand side, Technical Program Manager, Alessandro Festa. He is our Containerization expert. And we like to talk about containerization, maybe using Docker, which is our preferred product for that. And the first question could be, hey guys, why we are doing that with One Identity and Identity Manager?
All right. Well, I'll take that one. So I think that there's kind of three main reasons why we kind of decided to pursue support for containerizations, more specific to work around Docker One innovation.
It's part of One Identity. It's one of the things that we want to be proactive. We want to be able to support the latest and greatest technologies that are out there, numerous forms of APIs.
And I think containerizations being able to support that, and adding that supportability as part of our products will help customers and partners that are going to be deploying new products to the various customers. Two, I would say standardization, and really in regards to how our customers and partners are deploying, allows them to standardize and a better process in how our products get, not only applied, but utilized, and also able to adopt various new technologies by perhaps leveraging a hybrid model where using Azure or Amazon and so on to deploy some of the components of our products in a hybrid scenario. Third, I would say TCO, total cost of ownership plays heavily here, which will allow folks that are deploying customers and partners to perhaps reduce footprint of some of the components that we have, allows us to then used orchestration or cloud based orchestrations to provide a better method from a scalability standpoint, especially in large deployment. I think those are kind of the three that comes to mind.
Cool. Yeah. I mean, absolutely. I get [INAUDIBLE] Alex being in this case, because especially from an innovation standpoint, what we recognize is that the world is changing. And obviously, we need to cope with these changes.
And for example, it's in the nature of this company actually to follow the trend and follow the edge technology. And containerization is one of them. It's what we expect to see from customers, and what we expect to see from partners. Going to ask us more and more this type of technology. And this is really not an easy way actually to have them to follow this technology.
And really short, containerization, it's fancy. It's a cool feature. But a good question here is as well, which type of customers we think will use those containerization features?
Well, I can jump on this. Well, basically, I think that what you are thinking is like, we are not only looking at the typical identity professional. We are looking at other angles in a customer and the partners' environment. And for example, if we look at the dev ops, we look at the [INAUDIBLE], the way actually is deployed from a customer, would we expect in this environment more and more people actually can request containers. They are looking for use containers in their environment.
So they expect naturally to-- from vendors like us-- to supply these kind of technologies. So it's more a different approach is not related to business. It was related to [INAUDIBLE]. It is related to DevOps. It's related to the people actually that they deploy.
Today they deploy VMs, virtual machines. Tomorrow they will ask for containers. And these containers can be on prem or could be on cloud. And this is really good way to basically to reply to their request and still be the [INAUDIBLE] as we are today.
Another question could be talking about containerization and looking, for example, at a product like the Identity Manager, which is a solution framework. Which part of that solution frameworks could be a good part to be put in Docker containers? Or can you put the whole product in there? Or how we will do that? What is the idea of putting things into Docker containers?
Well, one of the scenarios where we see containerization really fit the bill is in the roles of identity manager. So if you think for example, of the job service role, or you think of the web portals or the applications service roll, then we see that when we use virtual machine in this kind of Identity Manager roles, we have a waste in [INAUDIBLE] consumption of CPUs, memory, and this space. That's not because of Identity Measure but because of that virtual machine itself is not optimized to run one single application.
When you said you go into a container work, you have a layer that is optimized to do that. You don't use the resources that are needed to be in that very moment. So from that point of view, and this is linking back what Alex was saying at the beginning is that this helps you to consolidate your instances and obtain your reduction of your total cost of ownership.
And but not only, it means that you have a positive spin up of the instances. And you can absolutely scale them more quickly. So it's more efficient to [INAUDIBLE] out.
So looking at identity management means that I can optimize resources, reduce the number of [INAUDIBLE] that running these instances, and obtain a general optimization all my [INAUDIBLE]. And that's why actually the containers were useful. It doesn't change the product, but at the same times, it optimized the products used.
Alex, with which product version, from your perspective, we will support Docker containers and identity management. We know we are
15:55
