Virtualization vs Microservers

I was talking to a friend of mine about where servers are going. He happens to be a network engineer and I tend to be surprisingly helpful with his server issues. It never hurts to be a good sounding board. Anyway, back to the story. We were talking about servers. I was asking him about how virtualization was doing. He explained that its a nightmare. I asked why… He said “the nature of servers is that their hardware fails. The problem with virtualized servers is that typically everything hinges on the hardware in one particular server or whatever server you are virtualizing from.” So I said, “its like the idea of mfps. Everything all in one machine. So if the that one machine fails. You cannot fax, print, scan or copy. Now back over to the server so if the server fails then all applications and operating systems virtualized on top of it fails.” “And the most important thing with anything is downtime”, he continued. So he is looking at microservers. A bunch of dumb servers. A server for an application. A server for an os. Servers that are dedicated to each individual application or os. This way if one fails its not the whole network and redundancy and load balancing really works. I asked him what about pricing… He said… “job security” and with that we finished our beers…. Then he continued… “what if the big boss is working on an important presentation and we have a server failure. If the downtime for the repair is 30 to 60 minutes or the downtime for the repair is a couple hours to a couple of days. That is the difference between virtualization to microservers- job jeapardy or job security”

Related External Links

This entry was posted in Network, PC Protection and tagged , , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>