Universities are starting to explore the future of the cloud. This future starts by getting rid of the many layers that separate software from physical hardware or bare metal. Currently you need a hypervisor (e.g. Xen, KVM, VMWare), an operating system (e.g. Linux, Windows, Mac OS), a language virtual machine (e.g. JVM), an application server (e.g. Tomcat, JBoss, etc.) and then the application.
In this article, researchers and academics are arguing that there is too much abstractions going on that could be removed in benefit of unseen performance. Projects like Open Mirage, Exokernel and Apache Mesos are examples.
If telecom operators want to offer IaaS and PaaS then they should focus on having a competitive edge that is not currently offered by established providers like Amazon and Rackspace. This competitive edge could be to build a new Cloud OS that has storage and processing nodes that run as close as possible to the bare metal. Building data storage solutions like Hadoop or Cassandra close to bare metal hardware and using the latest solid state drives would offer unseen performance. The cost per user would be substantially lower then less optimized set-ups. Ideally PaaS platforms can be delivered that allow “cloud application servers” to run on base metal. The model would be Heroku on bare metal instead of on Xen+Linux+JVM+App Server+Java App.
Telruptive is changing focus…
- Hadoop for Real-Time: Spark, Shark, Spark Streaming, Bagel, etc. will be 2012's new buzzwords
- Presto - Facebook´s Exabyte-Scale Query Engine
- 10 ways telecom can make money in the future a.k.a. telecom revenue 2.0
- Real-Time Hadoop queries will be a reality in 2013
- 5 Strategies for Making Money with the Cloud
- Trident Storm, Real-Time Analytics for Big Data
- 5 hardware trends to watch...
- Mesos: Your next highly distributed Cloud architecture framework
- Mobicents ' Restcomm is to Twilio what Eucalyptus is to Amazon
- Disruptive Innovations that can Kill the Telecom Industry
The Top Blogs
Want to reproduce a Telruptive post?
- Presto - Facebook´s Exabyte-Scale Query Engine wp.me/p144kK-fl 3 days ago
- MapD - Massively Parallel GPU-based database wp.me/p144kK-fh 1 month ago
- A Big Data-Base that is fast but inaccurate: BlinkDB wp.me/p144kK-eT 2 months ago
- Build your own 4 G LTE pico cell, GPS receiver, Bluetooth, zig bee, etc. wp.me/p144kK-db 2 months ago
- AWS awkward features Amazon should fix and enterprise features to add wp.me/p144kK-d9 3 months ago
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
All the contents of the Blog, EXCEPT FOR COMMENTS AND QUOTED MATERIAL, constitute the opinion of the Author, and the Author alone; they do not represent the views and opinions of the Author’s employers, supervisors, nor do they represent the view of organizations, businesses or institutions the Author is a part of.
The Author is not responsible for the content of any comments made by the Commenter(s).
While we have made every attempt to ensure that the information contained in this Blog has been obtained from reliable sources, the Author is not responsible for any errors or omissions, or for the results obtained from the use of this information. All information in this Blog is provided "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information, and without warranty of any kind.