August 5, 2011, by
Posted in Cloud, Thought Leadership

cloudwashingThere is a lot of Cloudwashing taking place in the industry today where more established ‘legacy’ vendors are simply rebranding or repackaging existing products and not fulfilling the real potential of Cloud Computing. They often host their products in Cloud environments so they can market their solutions in the “Cloud” category, but at the end of the day it’s still one instance of software and they can’t offer elasticity, horizontal scalability or multitenancy of “true Cloud” based solution.

To understand some of the key differences between the “true Cloud”, and the on-premises software model, companies need to focus on three components: cost, procurement/deployment cycle and expertise:

  1. Cost – A “true Cloud” solution is less expensive in terms of server-to-server comparisons than an on-premises deployment.  An example of this might be when using a cloud service for one project (for a period of time), scaling existing services or simply stopping using it. This elasticity allows you to meet changing capacity demands, deploying and releasing relevant necessary resources on-demand without costly infrastructure changes.
  2. Procurement/Deployment Cycle – With on-premises software solutions, the time it takes to get up and running can be challenging as companies struggle to determine server needs and integration requirements for their environment.  With a “true Cloud” solution, users can conduct business instantaneously, or within 24 hours when customization is preferred.  Horizontal scalability, or adding additional bandwidth, resources or storage to meet business requirements, is seamless and will not interrupt operations.
  3. Expertise – With any on-premises software, companies, or for that matter, vendors need to have the expertise to provision, secure, maintain, update and support the installation. With the “true Cloud” model, the benefit of economy of scale plays a part in support, updates, R&D and services which are all built on the same platform.  Some vendors call this repeatable success, however another term used to describe this would be multitenancy, which is the ability of software to be offered to multiple user entities (tenants) in a way so that each tenant operates as logically isolated while, in fact, using physically shared resources.

In my first blog post for Thru, since leaving Gartner, I wanted to highlight some of the key reasons why Thru is so successful in the market, while, at the same time, opening the floor up for discussion.

In this blog, I will continue to highlight Thru’s current capabilities and how the trends that we see in the market are influencing our product direction.

This site uses cookies to provide a better user experience. By proceeding, you consent to the use of cookies.
For more information, refer to the ‘Thru Use of Cookies’ section within our Privacy Policy.