Use PaaS to Decrease Ongoing Application Maintenance Costs

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

Unlock

This content requires an active subscription.

Access this content by logging in with your Info-Tech Research Group membership or contacting one of our representatives for assistance.

Speak With A Representative Sign In
or Call: 1-888-670-8889 (US) or 1-844-618-3192 (CAN)

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.

Get the Complete Storyboard

See how all the steps you need to take come together, with tools and advice to help with each task on your list.

Download Now

Get to Action

  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 Implementation icon Guided Implementation

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

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.

Activities: Outputs:
1.1 Identify key stakeholders.
1.2 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.

Activities: Outputs:
2.1 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.

Activities: Outputs:
3.1 Map PaaS opportunities to PaaS services.
  • ROI analysis for moving to PaaS.
3.2 Prepare rollout based on a project dependency timeline.
  • Project rollout plan for PaaS. ROI analysis for moving to PaaS.

Workshop Icon 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 road map in place to complete your project successfully.

Book Now

Application Development Map

GET HELP Contact Us
×
VL Methodology