Trial lock

This Research is for Members Only

Not a member? Unlock a free sample of our research now!

Already a member?

Sign in now

Applications icon

Use PaaS to Decrease Ongoing Application Maintenance Costs

Take advantage of PaaS to offload components of your application development and deployment maintenance.

Unlock a Free Sample

View Storyboard

Solution Set Storyboard Thumbnail

Your Challenge

  • The organization currently has many applications that use the same type of back-end and mid-tier components, leading to duplicate service usage.
  • With increasing sprawl, the app dev team can no longer sustain the resource overhead of maintaining the existing application portfolio while conducting development.
  • Platform-as-a-Service (PaaS) vendors sell the benefits of PaaS but you need an ROI-based business case to be built for PaaS recommendation.

Our Advice

Critical Insight

  • PaaS is not suitable for all projects. Carefully select pilot projects that have the greatest chance of success and determine the right requirements or risk significant cost overruns to fix problems or roll back development.
  • Selection of pilot projects can be a significant undertaking.
  • PaaS rollout may require peripheral projects to be accelerated.
  • PaaS will modify internal roles and processes. Get ready for change management.

Impact and Result

  • PaaS can offer an economic outsourced model for common application development components, similar to reusable libraries for non-cloud solutions.

Research & Tools

1. Map the applications suitable for PaaS

Determine a starting point for architecture discussions that will drive reusability.

2. Find where PaaS can help

Gain an understanding of what options are available and select the right ones.

3. Map PaaS services to needs

Analyze which services are most suitable to carry forward.

4. Monitor the rollout

Manage stakeholder expectations and the budget for future phases.

Guided Implementations

This guided implementation is a four call advisory process.

Call #1 - Select the applications

Identify the most valuable applications based on services needs and deployment flexibility.

Call #2 - Document PaaS opportunities

Determine where applications can be optimized according to your system architecture. Keep development and maintenance improvements in mind.

Call #3 - Select the right PaaS services

Determine the fit of all possible PaaS services to enable your opportunities based on ROI, cost, and people, process, and technology impact.

Call #4 - Rollout and monitor PaaS

Inform key decision makers of the PaaS rollout, highlighting any cost deviations, unexpected impacts, and overall rollout success. Establish a monitoring plan and discuss the next steps.

Onsite Workshop

Discuss This Workshop

Book Your Workshop

Onsite workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost onsite delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

Module 1: Map the Valuable Apps

The Purpose

  • Identification of key stakeholders.
  • Identifying applications important to the business.
  • Discussion around current system architecture.

Key Benefits Achieved

  • Common understanding across stakeholders of architecture for applications under PaaS consideration.




Identify key stakeholders.


Identify the appropriate applications to consider for PaaS.

  • Shortlist of suitable applications for PaaS.

Module 2: Identify Your PaaS Opportunities

The Purpose

  • Use the system architecture to drive out potential PaaS opportunities.

Key Benefits Achieved

  • Mapping of duplicate architectural components can help facilitate discussion around consolidation.




Assessment of current architecture for reusable components.

  • Mapping of PaaS consolidation opportunities to PaaS services.

Module 3: Implement PaaS

The Purpose

  • Select the right PaaS services and run through a ROI analysis to determine suitable pilot projects.

Key Benefits Achieved

  • A ROI business case for moving to PaaS.




Map PaaS opportunities to PaaS services.

  • ROI analysis for moving to PaaS.

Prepare rollout based on a project dependency timeline.

  • Project rollout plan for PaaS. ROI analysis for moving to PaaS.

Search Code: 74163
Published: February 7, 2014
Last Revised: February 7, 2014