Managing an effective hybrid architecture and cloud migration

SAMU is the next generation of enterprise architecture tools. It helps you to identify the right targets for cloud migration, perform the job and keep the services in sight in an enterprise context.

1. Identify the right targets

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.

2. Cloud migration

Regardless its type IaaS, PaaS or SaaS, you will need to create a migration plan with timelines and dependencies. The road leads through answering questions like this:

What applications will be implemented on the cloud platform or machine?
What are the main functionalities of the new SaaS application?
How will that support the business processes and capabilities?
What kind of data entities are processed outside?
What are the required integrations? Integration technologies used, platforms, network or security zones?
Are any data migrations necessary?
Which servers or applications can be retired as a result?

Plan and follow the migration projects and their architecture impact centrally

Plan the migration projects and their architecture impact

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.

3. Operate 24×7

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.

Automatic visualization of cloud environments (AWS, Azure, SalesForce)

See how

SAMU supports cloud initiatives in multiple ways

Identifying the dependencies in the hybrid architecture end-to-end

Planning changes in an enterprise context

1-click impact analysis spreading up to business processes