Java Reference
In-Depth Information
It's important to note that the placement of the offerings on this diagram does not
indicate preference or correlate with value in any way. Each of these offerings has its
own unique value and place in the market. And, in many customer scenarios, we've
used a combination of these to build the best solution. In fact, both authors of this
topic work for a consulting firm (with over 200 people) that has yet to purchase any
hardware. We are completely focused on cloud solutions and run our entire business
within the three offerings shown in the diagram.
Find More Time to Innovate
Take a look at Figure 1-2, which shows two diagrams comparing the scope of activities
and the budget and effort of a traditional IT department with those of another IT
department that is leveraging a PaaS offering for its business applications. Take special
notice of the amount of maintenance on the hardware, middleware, and application
layers for the traditional IT department. It's apparent that all that lost time is intruding
on the time, budget, and effort left over for innovation. Now, in comparison, consider
the IT department leveraging PaaS offerings for their hardware and middleware layers.
Removing the maintenance required to keep those layers in house, the department is
free to spend that extra time innovating on its core business applications. You might
notice that vendor management is a new time-allotment category when you're using
PaaS solutions. However, that's a small effort in comparison to managing these
solutions internally.
Figure 1-2. Tradional IT versus IT leveraging PaaS (Source: Appirio CIO blog)
Search WWH ::

Custom Search