30.01.2015 Views

u3Zgz

u3Zgz

u3Zgz

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

These materials are the copyright of John Wiley & Sons, Inc. and any<br />

dissemination, distribution, or unauthorized use is strictly prohibited.<br />

Chapter 2: Getting into Platform as a Service 17<br />

consistency in the management of the development lifecycle.<br />

Additionally, PaaS provides ease of provisioning in runtime<br />

services, including application runtime containers for staging,<br />

running, and scaling applications.<br />

Minimizing friction with IT<br />

Traditionally, when a new application server or other middleware<br />

was introduced into an organization, IT needed to<br />

make sure that the middleware could access other services<br />

that were part of the application. Development and Quality<br />

Assurance (QA) had to wait for IT to help them with this —<br />

sometimes causing intradepartmental friction.<br />

With PaaS, conflict is minimized because all middleware is<br />

easier to manage and connect.<br />

Improving the control over IT resources<br />

In PaaS, resources can be acquired from a pool of shared<br />

software assets by using a self-service process. When the<br />

resource is no longer needed by the developer, it can be automatically<br />

returned. This empowers development and QA to<br />

drive processes and reduce demands on IT.<br />

Improving collaboration<br />

PaaS changes the way that development and operations interact<br />

with resources. Instead of traditional application development<br />

being hand offs, with PaaS, the state of software becomes<br />

more visible to the organization. For instance, a developer may<br />

say that a module of an application is complete, but he hasn’t<br />

tested it on all Web browsers. With PaaS, the team can see<br />

whether software is working, broken, ready to be released to<br />

manufacturing, staged, and so on across the entire application<br />

lifecycle. You can buy this functionality, but it’s native to PaaS.<br />

To leverage many of the benefits of PaaS, you may need to<br />

make a tradeoff. For example, if you want to update your<br />

application and choose to go with tools that aren’t part of the<br />

prescribed environment, the process can still be done, but<br />

you lose some of the efficiency of working within a more controlled<br />

environment. If you break the mold and do it outside<br />

the framework, you need to do it manually. In other words,<br />

you can be locked into the vendor’s platform tools.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!