Use PaaS to Decrease Ongoing Application Maintenance Costs
Take advantage of PaaS to offload components of your application development and deployment maintenance.
Onsite Workshop
The increased app complexity and resource constraints in today’s fast moving business context result in:
- Increasing pressure to maintain existing applications with less resource and budget.
- Fragmented architecture components across multiple applications.
- Lack of cloud platform elasticity.
Making an informed decision about PaaS adoption can result in:
- Consolidated architecture in the cloud.
- An ROI-based roadmap to determine the right rollout strategy instead of ad hoc which would make downstream consolidation much more difficult.
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. |
|
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. |
|
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. |
|
3.2 | Prepare rollout based on a project dependency timeline. |
|