Obtaining an infrastructure, platform or software as a cloud service can make good business sense. However, to make the right decisions in terms of what and how to migrate to the cloud is not always easy – it is necessary to identify the potential targets where benefits outweigh the challenges. The risks from dependencies and service levels must be evaluated and mitigated.
Depending on what you source into the cloud you will need to create a migration plan with timelines and dependencies:
- IaaS: the existing infrastructure will be replaced by cloud infrastructure. You can plan what applications will use it and how to move them onto the new cloud infrastructure. It is also important to think about the data entities you will store outside your company and how users will access those.
- PaaS: sourcing a platform from outside means that you will need to think about the applications to be serviced with it. Is it an integration platform? Application connectivity and data security will definitely be a hot topic.
- SaaS: if you are shutting down an application in order to replace its functionality from SaaS, you probably will need to migrate data from the old system into the new. The application service will not be isolated, but integrated with your existing in-house or external systems. These connections must also be created.
Plan and follow the migration projects and their architecture impact centrally
This is the design of an example project, which aims to move out the Payroll Calculation business process to an external organization. The internal process will be inactivated together with its supporting application. The outsourced process is expected to be based on a cloud payroll application, and integrated to internal systems.
Orchestrate the project execution, identify dependencies and resolve conflicts
The above example project conflicts with other projects: they all touch at lest one architecture component at the same time – in this case, this is the HR management system. SAMU can highlight all these potential problems so project teams can resolve them at an early (cheap and low risk) stage.
Just because you buy it as a service and it’s outside in the cloud, it still belongs to your architecture. Any outage will impact your business and you need to manage this. Changes you will require or that are proposed by the service provider must be evaluated prior to applying them.
Know the business impact of changes on the service chain. This example shows a virtual server sourced from the cloud, which runs the production instance of the corporate Active Directory. Any changes in this server will have an impact on a number of integrations and business processes.
Are you managing a hybrid architecture?
Let us show you how SAMU can support you!
Sign up for a personalized demo now …