Skip to content

Cloud Migration phases

  • Assess: hardware, performance requirements, compliance, security, application dependencies, licensing
  • Plan:
  • Pilot: learn, validate performance, identify differences, revise scope
  • Deploy:
  • Move data: historical and active data
  • Move applications: types of migrations:
    • Lift and Shift: for quick, cost-savings measures. eg Netezza license expiring
    • Improve and move: take time to take advantage of cloud technology
    • Rip and replace: rewrite, useful for deprecated, obsolete systems
  • Optimize: Take advantage of cloud
  • Cloud Monitoring, deployment manager for resource provisioning,

Assess (Requirement Analysis)

  • Why: What is the problem that the proposed system is trying to solve? Also help define KPIs and SLOs
  • Who: are users, developers, stakeholders, SMEs
  • RACI: Responsible (Developers, Architects), Accountable/Approver (stake-holders), Consulted (SME), Informed
  • What: are main features, does the system do, are the roles (functional requirements)
  • role describes objectives, not a user title, maybe non-human eg downstream application
  • roles examples: Shopper, Account Holder, Credit Card User etc (not the actual users)
  • A persona represents different users with different needs e.g.
    • A busy mom needs convenience of shopping over price
    • A student will seek best prices over convenience
  • When: do users need the solution, will the developers and resources available (risks)
  • How much: data, many users (non functional requirements)