and move toward an inside-out approach: use PaaS in-house, then expand its use into the public cloud, including deployments of new applications.
Apprenda users may not only deploy new applications to Azure but also conduct Apprenda-based development there as well, if they choose, said Gary Olah, Apprenda's VP of business development, in an interview. In the future, customers may choose which type of computing they wish to use without worrying about enterprise boundaries. One Apprenda license will allow them to provision and occupy servers sometimes on-premises, sometimes in the cloud. As customers grow used to Apprenda's capabilities, they will compose rules that guide whether an application is deployed on-premises, due to security and regulatory requirements, or to the public cloud.
"As long as they keep buying Apprenda (annual subscriptions), they will get capacity on Azure," said Olah. Right now, those subscriptions assume most applications will be developed for use on premises, but in the future, the balance could shift toward heavier cloud deployments, he said.
Apprenda functions as a runtime environment, allowing applications to be deployed and scaled under its management provisions. Right now it includes automatic access to use of an open source Tomcat application server for Java applications. By the end of 2014, that access will include the Red Hat JBoss application server and IBM WebSphere application server as well, said Jesse Kliza, senior director of marketing, in an interview.
Can the trendy tech strategy of DevOps really bring peace between developers and IT operations -- and deliver faster, more reliable app creation and delivery? Also in the DevOps Challenge issue of InformationWeek: Execs charting digital business strategies can't afford to take Internet connectivity for granted.