Voting period for this idea type has passed

Cloud Portability With Multi-Cloud Toolkits

It's a multi-cloud world but your code needs to run somewhere. However, the Infrastructure as a Service cloud you choose today may not be the cloud you need tomorrow. Changes in reliability, performance, cost, and privacy may drive you to research alternative public clouds, a private cloud, or a hybrid of the two.
Considering cloud portability upfront can be crucial in avoiding lock-in. The tools you use to interact with the cloud will play a large part in how portable your code is between clouds.
In this session you'll learn how to effectively use software development toolkits that operate across multiple clouds. Find out how to distinguish between the layers of abstraction to achieve maximum portability or utilize cloud specific features. I'll show examples of multi-cloud toolkit code for Java (jclouds), Node.js (pkgcloud), Python (libcloud), and Ruby (fog).

Additional Supporting Materials


  1. Why is cloud portability important?
  2. How can I avoid being locked in to a particular cloud provider?
  3. What options are there for me when I need to programmatically control cloud infrastructure?
  4. What does a multi-cloud toolkit do?
  5. How do I ensure I'm using a multi-cloud toolkit effectively?



Everett Toews, Developer Advocate, Rackspace

Add Comments

comments powered by Disqus

SXSW reserves the right to restrict access to or availability of comments related to PanelPicker proposals that it considers objectionable.

Show me another