The Hypervisor predictions are becoming reality pretty soon with MS and Novell having partnered on the Hyper V and provding SUSE Linux as the first enligtened guest operating system on this platform.
Hyper V now comes with the MS Windows Server 2008 as an additional option.
However what will be more interesting is to watch the consolidation attempts of data centers in this period of economic flux. My prediction is that even with the advent of Hyper V and the existing VMWare solutions available etc. the CIOs and Data Center managers are going to look closely at cloud computing to go green and economically lean at the same time.
More applications are going to get written to be ready for cloud computing than ever before in 2009. Also in 2009, a lot of server consolidation is naturally going to happen using VMs however the future truly is the cloud. The natural problems these initiatives bring are the hares versus the turtles. The turtles will closely watch the hares and see where the pitfalls lie in this new embrace of virtualization.
One thing is certain, the economic necessities of the times are going to favor those who start embracing the concepts of a virtual world earlier than later.
Friday, January 23, 2009
Saturday, January 3, 2009
The art of being positive
The maturing of the IT industry is finally near us. I see that the IT governance practice, componentization of solutions to be assembly line processes and SOA based architecture along with associated concepts like SAAS (Software as a service) have taken us to to a stage where the act of management is the key to a thriving IT shop.
Generally speaking, the hit and miss days of IT are over now (or should be - those who are still in the dark ages need to evolve soon)
What does this mean for the projects and management of those projects. The management will entail taking a very positive attitude towards IT solutioning. This means past failures and "sunk" money should not deter an organization from investing or innovating. It is important since the costs to innovate are low enough currently and the benefits are high. A mashup or a set of services can be brought to bear upon a business problem in a matter of days and the worst case scenario is that one of the services will have to be replaced with another which provides the same facility.
The need of the hour is to make certain that the managers stay focussed on the arameters of success in the new world - long term efficiency and scalability instead of short term deadlines and stability. The evolution process of software has to be more pilot - test - prime and deploy rather than build - test - fix - test - deploy which is the traditional cycle.
The difference is in the service layer. If the service layer has to be developed in house, then the processes and management of the development of those pieces may still need the old rigor, but the consumers of these services should be able to continue in a more assembly line, quick to market and multi channel deployment path as a result.
Generally speaking, the hit and miss days of IT are over now (or should be - those who are still in the dark ages need to evolve soon)
What does this mean for the projects and management of those projects. The management will entail taking a very positive attitude towards IT solutioning. This means past failures and "sunk" money should not deter an organization from investing or innovating. It is important since the costs to innovate are low enough currently and the benefits are high. A mashup or a set of services can be brought to bear upon a business problem in a matter of days and the worst case scenario is that one of the services will have to be replaced with another which provides the same facility.
The need of the hour is to make certain that the managers stay focussed on the arameters of success in the new world - long term efficiency and scalability instead of short term deadlines and stability. The evolution process of software has to be more pilot - test - prime and deploy rather than build - test - fix - test - deploy which is the traditional cycle.
The difference is in the service layer. If the service layer has to be developed in house, then the processes and management of the development of those pieces may still need the old rigor, but the consumers of these services should be able to continue in a more assembly line, quick to market and multi channel deployment path as a result.
Subscribe to:
Posts (Atom)