Overview
The article discusses the complex migration of SlideShare's technology stack to LinkedIn's data centers, highlighting the challenges faced and the strategies employed to ensure a seamless transition. Key points include the integration of different technology stacks, the need for refactoring code, and the careful planning required for a successful cutover.
What You'll Learn
1
How to integrate separate technology stacks during a migration
2
Why refactoring legacy code is crucial for successful system transitions
3
When to implement read-only rules during a data center cutover
Prerequisites & Requirements
- Understanding of data center operations and migration strategies
- Experience with Ruby on Rails and database management(optional)
Key Questions Answered
What challenges did SlideShare face during its migration to LinkedIn's data centers?
SlideShare faced several challenges during its migration, including differences in network architecture, strict access policies, and the need to refactor legacy code that relied on specific naming conventions. These issues required careful planning and adjustments to ensure compatibility with LinkedIn's infrastructure.
How did SlideShare ensure a smooth cutover to the new data center?
To ensure a smooth cutover, SlideShare implemented read-only rules on the legacy data center and used software-based switching to manage write traffic. This careful orchestration allowed for a seamless transition while minimizing user impact and ensuring data integrity.
What was the significance of using a runbook during the migration?
The runbook documented all necessary steps for transitioning writes to the new data center, including ownership and duration of tasks. This ensured that the migration process was well-organized and that all team members were aware of their responsibilities, which was crucial for a successful cutover.
Key Statistics & Figures
Number of uploads on SlideShare
18+ million
This statistic highlights the scale of content that needed to be managed during the migration.
Number of professionals using SlideShare
70 million
This figure emphasizes the importance of ensuring a smooth transition to maintain user trust and service availability.
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Backend
Ruby On Rails
Used as the framework for building the SlideShare application.
Database
Mysql
One of the data providers used during the migration.
Database
Redis
Another data provider considered for the new architecture.
Database
Mongodb
Included as part of the data provider layer.
Database
Hbase
Also part of the data provider layer in the new architecture.
Key Actionable Insights
1Implementing read-only rules during a data center migration can prevent data integrity issues.By enforcing read-only access on the legacy data center, SlideShare was able to ensure that no conflicting writes occurred during the transition, which is a critical step in maintaining data consistency.
2Refactoring legacy code is essential when migrating to a new infrastructure.SlideShare had to refactor its code to eliminate dependencies on specific host naming conventions, highlighting the importance of adapting legacy systems to fit new environments.
3Using a runbook can streamline complex migration processes.The runbook provided a clear outline of tasks and responsibilities, which helped the SlideShare team execute the migration efficiently and effectively.
Common Pitfalls
1
Assuming legacy systems will work seamlessly in a new environment can lead to significant issues.
SlideShare encountered multiple problems due to assumptions about its legacy code and infrastructure, which required extensive refactoring and adjustments to align with LinkedIn's systems.
2
Neglecting to document migration processes can result in confusion and errors.
Without a well-prepared runbook, the migration could have faced disorganization, leading to potential failures during the cutover.
Related Concepts
Data Center Migration Strategies
Legacy Code Refactoring
Database Management During Transitions