Platform-as-a-service is becoming a common solution to build out an agile, Web-oriented business, but watch out for risks.
Editor’s note: The writer suggests PaaS started looking something like Force.com, as offered by Salesforce.com. It worked with Salesforce applications and will be used to provide new ones, provided you lived within its limits. But open-source PaaS, akin to Red Hat’s OpenShift, is way more general-purpose than that. The writer is a Red Hat employee.
As platform-as-a-service enters the mainstream with increased enterprise adoption, it’s vital for IT managers to have a transparent, five-point strategy.
Enterprises were reluctant to embrace PaaS within the early days by reason of vendor restrictions on application architecture and the chance of vendor lock-in. Modern enterprise PaaS offerings, mostly driven by open-source, are designed to attenuate these risks.
Still, it is vital for organizations to develop a technique that helps them profit from the immense benefits offered by PaaS while also minimizing the hazards. Listed below are the five pillars of enterprise PaaS strategy, that can help your small business mitigate the hazards while maximizing the advantages.
[Wish to learn more about another PaaS alternative? See Engine Yard PaaS Expands To Microsoft Azure.]
1. Ease of deployment and management: As private PaaS becomes the norm for enterprise adoption, key factors for IT to contemplate are how easy it truly is to deploy and the way steep the educational curve related to its management. Enterprises have already got large investments in IT infrastructure. In case you can leverage existing investments like load balancers and management tools for PaaS, it’s going to economize and accelerate the deployment.
2. Extensibility: As we move into the services world, smart organizations are embracing the postulate of “composable enterprises,” a term first utilized by Jonathan Murray of Warner Music Group. This indicates the platform must be modular and extensible. Just a platform with an open architecture gives you the extensibility had to build modern, composable enterprise platforms.
3. Data layer separation: PaaS vendor lock-in can happen in two ways: through restrictions at the application architecture, and thru the knowledge layer. Modern enterprise PaaS offerings are geared to lessen the constraints on application architecture, but it’s still important for IT to spotlight how the info layer is implemented within the platform. Data gravity means that if data is locked right into a particular platform or merchant, vendor lock-in will immediately follow. You must consider a platform where the information layer is loosely coupled with the platform in order that the price of migration from one platform to a different is minimal.
4. Role separation: Enterprises can offer platform abstraction for his or her developers in lots of ways. The simple approach is to make use of PaaS, but abstraction will also be achieved through an IaaS+ approach using DevOps tools like Chef, Puppet, etc. To make your mind up which approach is healthier, you would like to consider the desires of your company and your existing investments. An outstanding DevOps approach might involve developers learning operations and ops workers learning to code, or keeping the jobs separate but collaborative. An IaaS+ approach requires cross-pollination between the event and the operations teams, with each side learning the talents of the opposite. This approach is dearer, because it is hard to discover talent with expertise in both coding and operations. Counting on the platform, PaaS may help your company maintain separate development and operations teams while increasing collaboration between the 2. This approach not just increases your organization’s agility, nevertheless it also lowers costs.
5. Portability through standards: Although data layer separation keeps migration costs to a minimum, it is also important to think about whether PaaS uses industry standards to make certain application portability. Containers are fast becoming a traditional thanks to ensure application portability. Some platforms also use standard packaging formats for encapsulating application environments. Red Hat’s OpenShift Cartridges and Heroku’s Buildpacks are two widely known approaches to standardization in this front. Other PaaS vendors are embracing these two standards as part of their platforms.
As enterprises continue to acknowledge the worth of PaaS, we can see progressively more stories of ways they’re using it to maximise efficiencies. Ensure your PaaS strategy and investment delivers significant value with minimal risk.
Advanced persistent threats are evolving in motivation, malice, and class. Are you prepared to forestall the madness? Also within the new, all-digital The Changing Face Of APTs issue of Dark Reading: Governments aren’t the one victims of targeted “intelligence gathering.” Enterprises should be on guard, too. (Free registration required.)
More Insights