Is avoiding Cloud lock-in worth the effort?
Details
Have you ever heard someone say - "If you use that Azure specific feature/service we won't be able to migrate to AWS if needed".
A lot is said about trying to avoid being tied to a single cloud provider. But if you try to only use features common don't you lose some of the power of that provider?
Tools existing which abstract the provider and deployment away. Do these work? What complexity do they add?
Some advocate for a polycloud (using many providers) solution but doesn't that add more complexity and overhead.
How do you decide what's best?
Come join us we try to get to the bottom of some of this from 6pm on Tuesday February 19th at 1 New York Street, Manchester.
ECOM are kindly hosting us in their event space and are also providing pizza, beer, soft drinks and more.
As always this will be a group discussion. So please come and join in. This month we'll be discussing questions like: