Skip to main content

Ask yourself why do you need cloud migration

Before looking to cloud migration various factors need to be verified. Few of the are

  1. What is the business gain/value for the migration ?
  2. What is the organization goals in terms of cloud migration ?
  3. Rough estimation of migration cost vs business value
  4. What is the status of product life cycle ? Is it in sunset mode ?
  5. What are the COTS products used ?
  6. What is the license cost changes after migration if any ?
  7. Will you able to provide atleast AS-IS functional and non functional requirements of the application.
  8. What is the cloud migration strategy that benefit the clients, application and organization ?
  9. How to validate AS-IS functionality after migration. How many types of test cases are there ? Is there any need to create new test cases ? (Devils are in details)
  10. What is the level of data confidentiality ?
  11. What are the readily available cloud features help to reduce the cost of application ?
  12. Is user authn and authz are same after migration ? How to migrate users to new platform ?
  13. What is the disaster recovery plan ?

Below are the cloud migration strategies:




Cloud migration involves moving applications, data, and other business elements from an organization's on-premises infrastructure to a cloud computing environment. There are several types of cloud migration strategies, each with its own advantages and challenges. Here are some common types of cloud migration:

  1. Rehosting (Lift and Shift):

    • Description: In rehosting, also known as "lift and shift," the goal is to quickly migrate applications and data to the cloud without making significant changes to their architecture.
    • Advantages: It is a relatively fast and straightforward approach. It requires minimal modification to existing applications.
    • Challenges: May not fully leverage cloud-native features, potentially missing out on cost savings and performance improvements.

  2. Replatforming (Lift, Tinker, and Shift):

    • Description: Replatforming involves making some optimizations to the existing applications for better performance and cost efficiency while still maintaining the core architecture.
    • Advantages: Provides an opportunity to take advantage of some cloud-native features without a complete redesign.
    • Challenges: Requires more effort than rehosting and may not fully harness the benefits of cloud-native technologies.

  3. Refactoring (Re-architecting):

    • Description: Refactoring, or re-architecting, involves making significant changes to the existing application architecture to fully leverage cloud-native services and features.
    • Advantages: Maximizes the benefits of the cloud, including scalability, elasticity, and cost efficiency.
    • Challenges: Requires more time and resources compared to rehosting or replatforming. It involves redesigning parts of the application.

  4. Rearchitecting for Containers:

    • Description: Containers provide a lightweight, portable, and scalable way to package and deploy applications. Rearchitecting for containers involves containerizing applications for better consistency across different environments.
    • Advantages: Enables consistent deployment and scaling of applications. Improves resource utilization and facilitates easier management.
    • Challenges: Requires changes to the application architecture to work effectively with containers.

  5. Rebuilding (Full Rewrite):

    • Description: Rebuilding involves rewriting the entire application from scratch to take full advantage of cloud-native services and architectures.
    • Advantages: Offers the maximum benefits of cloud computing, including scalability, agility, and cost efficiency.
    • Challenges: Requires significant time, resources, and expertise. Often chosen for legacy applications that need a complete overhaul.

  6. Hybrid Cloud Migration:

    • Description: In a hybrid cloud migration, organizations maintain some applications and data on-premises while migrating others to the cloud. This allows for a gradual transition and flexibility.
    • Advantages: Provides a balance between on-premises and cloud resources. Allows organizations to retain sensitive data on-premises while leveraging cloud benefits for other workloads.
    • Challenges: Requires careful planning and integration between on-premises and cloud environments.

The choice of migration strategy depends on factors such as the specific goals of the organization, the nature of the applications, and the available resources. Organizations often adopt a combination of these strategies based on their unique requirements.

Labels:

Comments

Post a Comment

Popular posts from this blog

OWASP API Security Top 10 vulnerabilities 2023

API Security Do's and Don'ts Don't trust input data for an API and do validate all inputs. Ensure you understand security and keep sensitive data out of code. Don't hardcode keys/tokens Don't reveal useful info in error messages. Don't have hidden/unadvertised features. Don't filter data in UI - control at app level Don't confuse authentication and authorization Always use API gateways to control access and traffic Do require API documentation. Do expect users/hackers to find and use undocumented endpoints Do continuous testing - attack simulation, test configs, fuzzing, injections OWASP API Security Top 10 Vulnerabilities 2023 API-1:2023 - Broken Object Level Authorization: BOLA is still the leading vulnerability that plagues APIs. When data objects do not have sufficient access controls in place, resources can be accessed by unauthorized users. API-2:2023 - Broken Authentication  Broken Authentication contains all vulnerabilities associated with auth...
Post a Comment
Read more

Load Balancer Routing Algorithms - Draft version

The main purpose of the load balancer is to distribute the traffic evenly across multiple servers. The Load Balancer promises the efficient usage of the back-end servers without overloading and not keeping the server in busy times. Avoiding the server overload will reduce the downtime. Table of Content: Different types of LB Algorithms used by ALB ALB Features  Questions Configuring ALB in AWS  Creating K8S config files Factors to consider to ALB design There are different types of load balancers: Application Load Balancer (Layer 7) Network Load Balancer Global Server Load Balancer Let's narrow our discussion to Application Load Balancer(ALB). The ALB operates on layer 7 of OSI model.   Algorithms used by ALB are: Round Robin   Least connections Weighted Round Robin IP hash Least Connections Response time The ALB evaluates incoming requests to ensure efficient and reliable traffic distribution. LB has to ensure. High availability Scalability Performance opt...
Post a Comment
Read more

React JS Basics

  What are side effects in React? In React, side effects are operations that interact with external systems or cause changes outside the component's rendering process. These can include: Data fetching: Retrieving data from APIs or other sources. Subscriptions: Setting up listeners for events or data changes. Timers: Creating timers for delayed actions or animations. DOM manipulation: Directly modifying the DOM (rarely used in modern React with declarative approach). Why use useEffect ? In class-based components, you would typically use lifecycle methods like componentDidMount , componentDidUpdate , and componentWillUnmount to handle side effects. Functional components don't have these methods directly. The useEffect Hook provides a way to manage side effects in functional components. It allows you to run a function after a component renders (or re-renders) and optionally clean up any resources created by that function before the component unmounts. How does useEffect wor...
Post a Comment
Read more