If you are trying to find out what the right hypervisor is for your private cloud or IaaS then you might be asking the wrong question…
Do most applications really need an OS and hypervisor is a better question?
One company of the companies that is exploring this area is Joyent. Thier SmartOS is like the mix between a virtual machine and a combined OS + hypervisor. Instead of installing a hypervisor, on top an operating system, on top an application server or database, the Joyent team thought it would be more efficient to try to remove as many layers as possible between the application/data and the hardware.
According to publicly available videos and material, their SmartOS is based on a telecom technology for high-scalable low-latency application operations. Unfortunately Google does not seem to be able to answer which telecom technology it is. So if you know the answer, please leave a comment.
The idea of running applications as close to the hardware as possible and being able to scale an application over multiple servers is the ultimate goal of many cloud architects. Joyent claims that their SmartOS runs directly on the hardware. On top of SmartOS you are able to install virtualization but ideally you run applications and data stores directly.
The next step would be to combine the operating system with the virtual machine/application server or database server into one. Removing more layers will greatly improve performance as can be seen by Joyent’s performance tests.
So the real question is: do we need so many extra layers?
A distributed storage system, a virtualized webserver, a virtualized app server, a distributed SQL-accessble database or NoSQL solution that would run straight on hardware with a minimal extension to distribute load over multiple machines would be the ideal IaaS/PaaS architecture. It would give customers what they really need: performance, scalability, low-latency, etc. Why add a large set of OS and hypervisor functions that at the end are not strictly necessary?
Most operators have a mobile portal in which end-users can buy games, applications, ringtones, etc. Several operators have a legacy of server hosting, email hosting, and other business services. Some operators have a marketplace where small medium enterprises can buy SaaS. Others are thinking or building a private cloud and want to become an infrastructure as a service provider. Often to avoid legacy hosting to disappear.
There can be reasons why a small, medium or large enterprise wants to use the infrastructure from an operator compared to a public cloud: SLAs, quality of network service, security, etc. Price is very likely not going to be one of them. Neither will be innovation or flexibility because here the likes of Amazon, Google and Microsoft are almost impossible to beat.
So why is it that operators think that IaaS is their preferred strategy to enter the cloud? I have no idea but my opinion is that it is easier to start with SaaS and work down to PaaS then to start at IaaS and work upwards. IaaS will have hyper-competition and very small margins as a consequence…
An alternative telco cloud strategy
Operators often have a direct sales channel towards medium-sized enterprises. By offering a SaaS marketplace they could extend the amount of services they are providing towards these medium enterprises. After reaching a tipping point, smaller enterprises will likely follow via direct web-based purchases. However reselling SaaS can never be a long-term strategy.
SaaS should be an initial start of a new customer relationship. Operators should focus on selling complete solutions focused on a specific industry or problem domain. Examples:
* Healthcare – web, mobile, tablet, TV and SMS patient reminder & reservation system, health-care call-center as a service, farmacy locator,web-based medicine reservation system, etc.
* Restaurant – web, mobile, tablet, TV and SMS table reservation system, online menu web hosting, group-based or community food purchasing service, special deals á la groupon.com, etc.
* Car dealers – web, mobile, tablet, TV and SMS maintenance reminder & reservation system, parts-locator call-center as a service, etc.
The operator should not focus on inventing these services but instead on creating the tools, the eco-system and the community for smaller IT shops and other to come up with scalable niche services.
To fully utilize a SaaS an SME needs help: training, configuration, customization, integration, etc. For this you need a services marketpace closely linked to your SaaS marketplace. As well as a long tail support solution.
The Long Tail Telco PaaS
To be really able to offer long tail services, operators need to have a long tail Telco Paas. A Telco PaaS is like a Google App Engine, combined with Google App Marketplace, combined with Twilio/OpenVBX, combined with charging on your invoice, combined with open standards like OpenID, oAuth,SIP, etc.
Not clear??? A small company knows best what another small company need. However they do not have the infrastructure to reach and help thousands of other small companies in the world that have the same problem. This is where the operator should help both with global communication and IT solutions. A small company should not be focusing on installing a CRM, call center, ERP, etc. if they want to help others configuring and customizing a health care reminder service. They should have specialists in the health care reminder service and should be able to purchase the rest from the Long Tail Telco’s marketplace. They should also be able to auction a request for legal assistance, escrow-service, translation, etc., basically an all-in deal. The operator should focus on business communication in the broad sense, not the telephone service sense…
There are several long tail sales channels that are currently showing results. Clear examples are Amazon, Netflix, Google, etc. However there is a key area that is currently not resolved: long tail post-sales support.
In the telecom world, operators are not launching long tail applications because they can not offer post-sales support. A lot of small innovative solutions are not meeting the public because the operator can not afford consumers or small businesses to call massively their call centers. Every call-center call costs €1 or more and training call center agents on thousands of niche applications is virtually impossible.
A director in a tier 1 operator told me the other day that what we are missing is the container for long tail post-sales support. His logic was that the second biggest invention after the Internet was the container and the pallet. They allowed goods to be shipped cheaply all over the world. The Internet accelerated the purchases but the container made it possible that China and others produced it and the rest of the world consumed it.
We need to find the container for long tail post-sales support. The simple solution that allows people to understand which services and solutions have a best-effort, basic or top-class support and to get their problems resolved in the shortest and easiest way.
What is the problem? An individual programmer can build a very successful application, launch it on a telecom cloud and get virtually overnight thousands of customers. This programmer would be totally overwhelmed with bug reports, feature requests, integration needs, customization needs, training needs, etc. from thousands of consumers and small businesses. A business can not afford a critical service not to be available during hours or even minutes or seconds. A single programmer might be a guru in building an innovative application but might lack basic skills in supporting it.
The same would be true if we talk about niche solutions, open source solutions, general solutions with long tail plugins, telecom PaaS platforms, etc.
So do I know what the container is? Not yet but I am actively reviewing different solutions. If you are interested in participating then drop me a line: maarten at telruptive dot com.