[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 always talking about roadmaps. We know we cannot directly say this is the truth or tomorrow you will get the following feature. But what is the plan behind containerization in the Identity Manager?
Great question. Well, obviously, it is a technology that can be used in theory with backwards or back releases of the product. We have decided to standardize. There are containers based on the version 8 release that would happen towards the end of last year. And we're going to continue to evolve those containers or those images as part of every release that we have.
So up and coming 8.01, there will be some slight updates to that. And we'll continue to maintain that. So from a supportability standpoint, I think we can easily say that is from version 8 and on. And also, I think Alessandro mentioned the fact of the job server being one of the components that would be mostly fitted to be containerized. So not just the job server will we be providing images not just for the job servers, but our goal is to also provide images for the application server and the web server as well.
--[INAUDIBLE] containerization, in One Identity and One Identity Manager. Do you have use cases we can support with containers today?
I mean, I guess. We kind of talked about this early around how each customers and could potentially utilize partners from an implementation standpoint. But I think there's kind of a three, maybe four relevant use cases.
One, obviously, from a customer standpoint. As they're getting push-- not push back, but getting pressure from a dev ops standpoint to start utilizing containers. We're hearing quite a bit from various customers that there's already a demand internally to start utilizing that new technology. So obviously, the pressure from a DevOps standpoint is going to increase. And they'll have to start adapting not just One Identity Manager, but any of the One Identity product portfolio or other products that they may have out there as well.
Two, I would say from our partner ecosystem standpoint, it kind of provides them the ability to actually create new type of deployment methodologies where they would then use this kind of hybrid scenario where some pieces maybe on prem. They could then utilize perhaps the cloud as well to do these types of deployments. Three-- and we'll see probably in the kind of a service provider managed service type of offering, where we may end up having a partner or somewhere else, some [INAUDIBLE] that may want to be able to kind of deploy the product itself in a way that they want to maybe provide Identity as a service offering to a customer base.
Yeah. I absolutely agree with you. I think that the message between these three scenarios is that all these three actors, they are trying to reduce the [INAUDIBLE] in different ways. But in the end, that's again, the same story about I want to optimize everything in my environment that is a cost related. Or anyways, just the way to optimize my job.
If you look at the customers, you currently [INAUDIBLE] is like, the [INAUDIBLE] is looking for ways to optimize the environment. That means I would like to deploy less virtual machines, I would like to speed up the time I need to spin up or spin down an instance. And all the typical scenario [INAUDIBLE]. And again, containers is really, really, really good for that. Is it's really a good fit for that.
[INAUDIBLE], on the other hand, looking for a way to optimize their job. If I'm a consultant, I really need to quickly move from one customer environment to another customer environment and do my job. And containers again, really helped them. And the service provider is the most interesting scenarios probably, because they run large environments from many, many, many customers. And they looking for a way to reduce the total TCO, because they have this large [INAUDIBLE] to run.
And containers really can help them. And so be able to support them, not only as you currently said Alex, not only from Identity Management, with all the product portfolio One Identity help us to put us our self again, and the innovation top quadrant of the Identity [? Managers ?] of the software [INAUDIBLE] anyways. And that's why we are here.
Remembering that all of our customers, just talking about a complex product, if they talk about the Identity Manager, especially because it is a solution framework to solve a complex problem. The question is by adding the container technology into One Identity Manager, is this increasing or more decreasing now the complexity?
Yeah. That's really good question. Well, we are not actually reducing the complexity of One Identity project, because obviously, we are not touching or changing the way we deploy a project from an identity perspective. But what we are going to reduce is the [INAUDIBLE] complexity. So if you should think again, we were discussing before that if we think about the way you deploy an [INAUDIBLE] in terms of Identity Manager, then you have to stop the VMs, you have to be sure that these comply with our best practices.
You have to set up more than one environment. So when you use a container obviously, all of these complexities dramatically reduced. You just issue a couple of commands, and the job is done. And probably there is other scenario where actually this complexity can be read reduced. What do you think Alex?
That this correct. I'm thinking mostly around hybrid scenarios where partners or customers are going to be looking to extend the current on prem deployments to start leveraging our containers. Right where you can then use elasticity of the cloud as a whole to then perhaps looking at some areas around scalability, and to be able to actually create or launch new [INAUDIBLE], it's a better word. It should say new job server specific to a job task. If I have a very large job task, then I need to do-- I may want to automate that to be able to then go ahead and generate multiple job servers for that specific task.
And when that's done, and I can then throttle back and use the current infrastructure I had in place. I think that is the definitely going to be a true advantage for customers that are starting more and more to utilize container technology, but I think more specific to our partners and then perhaps any other partners [INAUDIBLE] from a managed service standpoint, that wanted to then spin new environments quickly to provide service for other customers, that's obviously another advantage they'll be able to have that to do that.
And you make a great point because basically, we can leverage the native Docker capabilities [INAUDIBLE] of high availability and load balancing to [? hide ?] to Identity Manager. So from one side, we reduce the complexity of create a complex scenario where we need higher [INAUDIBLE] where we need load balancing. And we get this almost out of the box from the container [INAUDIBLE]. So we don't have to worry about anymore about this part of a project.
And then that results is actually the project probably spin up is way more simple from that point of view. And that's actually the partner or the customer itself actually to be more successful. And that's the [? ultimate ?] goal of every One Identity product in the end. [INAUDIBLE].
Thank you sirs for being here, and for [INAUDIBLE]. For you on screen, we just will continue in this video series which are showing you some simple samples with Docker, again, with Ales and Alex. And hopefully, you will have a lot of fun with these videos and you will learn something from it. And [INAUDIBLE] video, just [INAUDIBLE].
15:55
