Good stability, supports a hybrid model and easy to use There is an area of improvement. For example, you are migrating from a customer's existing data center to a new target data center. To facilitate this transition, you'll initially need to evaluate the customer's aging hardware hosting VMware, which is nearing the end of its operational life. The customer expresses the intention to upgrade to a newer version, necessitating an overhaul of everything in the new data center. As a Systems Integrator (SI), consultant, or architect, your recommendation would be to acquire the latest hardware with a specified configuration and then install VMware on top of it. However, there's a crucial aspect related to the infrastructure requirements for VMware to run seamlessly on that hardware. If there's an opportunity to potentially reduce these infrastructure prerequisites, it would be highly beneficial. This is because a higher number of VMware licenses requires more infrastructure capacity from Original Equipment Manufacturers (OEMs) or Colocation partners. Consequently, when discussing the operation of this virtualized environment from VMware over a contractual period of five years, the overall cost to the customer is influenced by the infrastructure requirements. If there's a feasible way to decrease these prerequisites for the infrastructure supporting the virtualization layer, it would be advantageous in terms of cost for the customer. Any customer in today's world exists or wants to exist in a hybrid model, so in future releases, we would like to see this. So, going forward, if this virtualized environment would exist, it has to be a combination of on-premise plus public cloud Azure/AWS. It should be more seamless when your interface or when you are interacting with workloads running on-premise VMware/AWS VMware. So it is only there in some capacity and space, and I'm aware of it. And Azure and VMware already have a tie-up on the same lines, but at the same time, if it is more seamless, if it is more interchangeable, if you could move your workloads, or if you can access your workloads or your virtual machines irrespective of whatever platform it is running, whether it is on-premises, or cloud or public cloud, it'll be a lot more comfortable for a user than the user to consume that infrastructure. Firstly, it needs to have a combination of deployment and be more seamless for the customers. Secondly, more software-defined features, more in terms of managing the infrastructure pool in a software-defined way. Managing the infrastructure pool in a more optimized fashion is going to be the key in the upcoming times. It's not just on-premise, but at the same time, it should also be the public cloud as well. Probably because when I meet my customers, this is one thing that I always tell them. I have seen people moving from on-premise public cloud only to realize at the end of the month that they end up paying a higher bill compared to what they were paying when they were running their business on-premise. The reason is that they do not understand or do not realize the full potential of the public cloud, and the way it should be consumed, the way it should be used, and the way it should be scheduled to ensure that the billing at the end of the month is very optimal. You pay for what exactly you need, not everything that you have from the cloud. That's not a way to use the cloud, whether it is on-premise or from the cloud. For example, an enterprise has over 100 applications. Out of that 100 applications, only 25 applications are running the production instances, and the remaining 75 are running non-production instances. It can be a development environment, a test environment, a sandbox, etc. In this case, you need to run only the 25 applications on the public cloud 24/7. You do not need to run your remaining 75 applications 24/7. Because, eventually, your developers, testers, quality managers, and whoever will use the non-production environment only when they're in the office and working on those applications. Then why do we need to have those applications, which are non-production in nature, lower environments? So we're running on the public cloud all the time because, for a cloud provider, it is a virtual machine; whether you are consuming it for production work or non-production work, it is going to charge you the same bill. And if you are not optimizing, if you're not scheduling workloads, you are actually wasting money. You're wasting your money, and your bills, which you are going to pay with the public cloud provider provided, are going to be bad. It's going to be crazy. And then customers do not know what to do in this situation. And you cannot fight with the public cloud provider because they would say, "I had given you all the possibilities, all the opportunities to learn about it, the way you should be functioning it, the way you should be utilizing it. If you are not using it the way it should be used, That's not my problem."
