Optimizing Cloud Migration: Performance Lessons for the Enterprise

Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/671893

Contents of this Issue


Page 17 of 35

also possible to use an A/B testing approach to roll out the new sys‐ tem to a small percentage of users and optimize it before rolling it out to the full user base. Starting small minimizes the risk of the move to the cloud and allows you to investigate the Internet performance at a point where it is still possible to move to an alternate provider. 2. Test, Test, Test—Prove Everything Before Committing to the Move The nature of the cloud is that everything is throwaway, you pay for what you use, and you can scale up and down at will. This allows you to try things out, see the reality of the situation, fail fast, and then move on. The systems you test on can also be completely live- like, giving the opportunity to do some full-performance testing. The benefits of this for functional correctness are well documented, but the impact on Internet performance is in some ways more important. It allows you to fire up systems, run tests from dis‐ tributed geographical locations, and monitor the Internet perfor‐ mance. The important takeaway here is that if there are issues, you can raise them with the provider. It's likely that the provider won't be able to do anything about those issues, but the nature of the engagement allows you to walk away and investigate alternatives. It also allows for an A/B type release, gradually releasing the systems to subsets of users to determine whether the testing you have done is still valid with those real users. Having proved the concept after testing shouldn't end the testing. After migration to the cloud, ongoing testing (either explicit testing or by validating real-world performance via monitoring) should take place to ensure that the solution is still optimal. Moving a cloud system into production doesn't necessarily require a long-term com‐ mitment or mean that that platform is set in stone—if it is not meet‐ ing requirements, then it should be modified. Don't be afraid to move clouds. 12 | Phase 2: Beginning Your Journey to the Cloud

Articles in this issue

view archives of eBooks - Optimizing Cloud Migration: Performance Lessons for the Enterprise