Cloud-First Strategy to Cloud-Native Landscape

Critical pointers to consider before formulating Cloud Strategy

  1. Analyze your IT Infrastructure & Application budget (CAPEX & OPEX)
  2. Create an Application Landscape with all interdependencies covered. (App to App integration and External parties integrations)
  3. Assess the type of data, volume of data being accumulated, and how business-critical data is backed-up.
  4. Align to Core Business Vision and their future road map.
  5. Take stock of the IT Department team size and internal IT Capabilities of the organization.
  6. Check the regulatory constraints in your organization’s line of business. (Eg: GMP for Manufacturing & Pharma, Central Bank norms for Banks., etc.)
  7. Consider the Data Privacy laws of regions your Organization does business.
  8. Application OEM dependencies on Cloud Compatibility. (Re-architecting or re-developing the Application in a cloud-native way)
  9. Stakeholders(Business and Finance teams) alignment on Cloud Transformation from On-prem.
  10. Cost transfer feasibility, within BUs based on utilization of Cloud services. Also, be mindful of the hidden cost of moving to the Cloud as listed below:

Cloud-Native Landscape

Once your cloud or cloud-first strategy has been approved within your organization, go for low-hanging fruits. To get an initial buy-off from important stakeholders it’s imperative to show quick wins. Look for applications which less critical, and easy to move in PAAS or SAAS model. Ensure these are light in data and don’t possess any critical data (Company’s IP or strategy).

  1. Setup DevOps practice in your organization (including revamping your developer teams with relative skills).
  2. Implement CI/CD Pipeline(covering both process and Automation).
  3. Toolsets to be procured or subscribed. The decision to buy a toolset is very critical to the success of automation in Application deployments.
  4. Implement SRE practice to ensure the Applications or solutions developed through a Cloud-native way are robust and reliable to consumers/customers.
  5. Move on to the DevSecOps model, to ingrain security practice in each and every step from the Build to Deployment phases of the Application.
  6. Comply with 12-factor application app principles.
  7. Bring PMO(Agile methodology) using JIRA kind of tool, integrate with Jenkins kind of CI/CD automation software.

Benefits of Cloud Native Landscape for your Application development

  1. Cloud economics or OPEX for Cloud hosting will be optimized. We can reduce around 50% cost when compared to IAAS’s way of just migrating the existing monolithic applications. Also, a Single Pane of Glass for a multi-cloud using organization will give a clear indication of available and utilized resources.
  2. If you are developing applications in a Cloud-neutral way, you can be a Cloud service provider-agnostic and leverage the latest features being introduced on regular basis.
  3. DevOps Practice, CI/CD Pipeline, and Cloud-native app development will give agility and optimal use of IT human resources.(eg: Netflix)

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
vijay raghavan

vijay raghavan

A simple person who wants to do little things right to change the society for Good.