Migrating from dedicated or colocated hosting to a cloud platform is an incredibly attractive option for many websites. Executives love the pay-as-you-use proposition without having to invest significant capital up-front for depreciating hardware and licenses. Infrastructure teams salivate at the possibility of quick, simple, and even automatic scaling capabilities. Application developers relish the thought of being like those “other companies” that seem to be able to do marvelous things because of their underlying cloud computing capabilities. (We could even have a Chaos Monkey!)
Initially, the migration path can seem straightforward and even deceptively simple. To startups and younger companies who have always been cloud-first, the challenges faced by more established enterprises in getting to the cloud can seem confusing. It can also be difficult to confront the fact that your existing processes and infrastructure are actively working against a straightforward migration to the cloud.
Rob Burke outlines the lessons learned and mistakes made when GameStop executed its migration to the cloud as well as a checklist of key decisions that need to be addressed before, during, and after a migration. Rob also shares GameStop’s postmigration experiences, where new and unforeseen challenges emerged as GameStop came to terms with its new capabilities and constraints.
Rob Burke is an engineering director with GameStop International, where he leads the teams that build GameStop’s ecommerce and multichannel platforms. Rob has over a decade of experience in building applications and leading and growing high-performing development teams. In recent years, his focus has been on building lean startup-like teams within a Fortune 500 organization to deliver significant value to internal and external customers without the typical “enterprise” tax.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org