Unpacking the Future: The Great Transition from Traditional Servers to the Cloud

Unpacking the Future: The Great Transition from Traditional Servers to the Cloud
Play this article

As someone who has worked in the domain of Cloud Migrations, I find myself immersed in the intricate world of transitioning from servers to the cloud. Here I will be unraveling the complex tapestry of cloud migration, drawing parallels with a relatable real-world analogy to make the understanding seamless.

The Evolution from Server to Cloud

Let's first go a decade back and hit some nostalgic notes

  • Microsoft Office

    • Then : Sold as DVD, each version required separate purchase

    • Now : Offered as Office 365, a cloud-based service with continuous updates and various subscription models

  • Video Games :

    • Then. : Sold on DVDs or CDs in physical stores.

    • Now : Platforms like Steam, Epic Games, and Xbox Cloud Gaming allow users to purchase, download, and play games via the cloud.

  • Operating Systems :

    • Then : Windows and other operating systems were often sold as DVDs

    • Now : OS updates are downloaded and installed via the internet, and some systems like Chrome OS heavily rely on the cloud.

  • Project Management Tools (e.g -> Jira, SAP ERP, Oracle DB ):

    • Then : Installed on company servers with a perpetual license.

    • Now : Offered as cloud services with various subscription models, allowing access from anywhere at any time.


But, Why is relying on Servers not a good strategy for both Consumers and Businesses?

  • Heavy Reliance on Existing Infrastructure and Personal Machines

  • Lack of Regular Updates, Bug fixes, Security Patches

  • High Distribution Costs

  • Expensive Software Updates

  • Piracy Issues

  • Absence of Automatic Data Backup and Recovery

  • Limited Accessibility from other devices or remote locations

  • Incompatibility and Integration Issues

  • Security Concerns

  • Environmental Impact

Now let's define Server and Cloud

Server (On-Premise) : In the server model, businesses own and manage their computing infrastructure. They bear upfront costs for hardware and software, in-house team manages security, compliance, and updates, aligning with specific regulatory requirements.

Cloud : Here the Company owns and manage the infrastructure, reducing businesses' upfront costs. This model ensures easy accessibility and scalability. Providers handle security and updates, allowing businesses to concentrate on core activities.


But What's the Problem here? We can just start using Cloud Services now, right? Think Again...

Businesses needs their system in a fully functional manner with all the Data and processes preserved. This is the tricky part

The data housed in servers is not monolithic; it’s diverse, spread across various platforms and formats, making migration a meticulous task.

For instance, a company using SAP for enterprise resource planning may face hurdles in migrating extensive historical data, custom modules, and integrations with other systems. The process demands careful planning to ensure data integrity and consistency, avoid downtime, and ensure that the new cloud environment aligns with the organization’s operational needs.


JIRA

The arts and crafts of Jira assets management | Salto

Let's take an example of JIRA, If someone is migrating from Server to Cloud what all needs to be taken care of and why is it such a complex task to perform

  1. User Data : In JIRA migration, user accounts, groups, and roles must be correctly mapped to maintain organizational structure and access controls.
  1. Permissions and Roles : Migrate permissions and roles to ensure that users retain their access levels and responsibilities in the new environment.

  2. Filters and Custom Filters : Safeguard all filters and custom filters to assure consistent data viewing and reporting post-migration.

  3. Boards and Projects : Move boards and projects, ensuring all data, configurations, and dependencies are intact.

  4. Configuration for Projects and Issues : Meticulously migrate configurations to ensure that projects and issues function as intended in the new environment.

  5. Dependencies and Attachments : Ensure all dependencies are maintained, and attachments are correctly linked to their respective issues and projects.

  6. Links and Timestamps : Preserve all links and timestamps to ensure data integrity and historical accuracy.

  7. Reports : Ensure that reports are accurately migrated to maintain access to historical data and insights.

  8. Workflow Transition : Migrating customized workflows and ensuring they are correctly set up and triggered in the cloud environment.

  9. Integration with Other Tools : Ensuring integrations with other tools and services remain intact, or reestablishing these connections post-migration.

  10. Add-ons and Plugins : Evaluating the compatibility of add-ons and plugins in the cloud environment and finding alternatives if needed.


Phases of Migration :

**1. Data Preparation

2. System Readiness
3. Maintaining Project States
4. Stability During Migration
5. Ensuring Consistency
6. Monitoring Migration Progress
7. Effective Communication of Progress, errors, warnings to Customer**

Evolution is Constant