Many of our clients have had bad experiences with vendor lock-in. Replacing an underlying technology or software package which forms a core part of your IT estate is fraught with complexity and cost. As AWS experts, here are our honest thoughts on cloud vendor lock-in.
Long tie-in contracts and annual license costs that rise year on year with little additional value, mean that a deal which seemed attractive five years ago can quickly become an expensive disadvantage. It can constrain both your competitiveness and annual budget. Then, it isn’t long before the services you provide are entirely dependent on a single technology vendor and you’re feeling held to ransom.
So it’s no surprise that when moving to cloud and considering their future technology strategy, many companies put “not being tied to a single vendor in the future” high on their list of priorities.
However, the past is not always a good indicator of the future – cloud is a completely different technology. While there are factors you must consider carefully before selecting a cloud vendor, some of the issues encountered with traditional technology solutions are less relevant.
When considering costs, you’re only paying for what you use. While it’s essential companies monitor their spend carefully and use cloud cost optimisation techniques to stop annual costs spiralling out of control, you will avoid paying for data centre space you’re not using. You won’t waste money procuring space to cope with future expansion, or time waiting for hardware to be delivered, installed and configured.
Interestingly, we’re seeing the cloud spend in most companies rise significantly year on year.
Teams are unconstrained so tend to spin up new environments rather than re-use existing ones. Few companies are accurately allocating cloud costs to teams based on their usage, so why should teams bother restricting their consumption? If they don’t use it then another team will, and they’ll still get allocated the same costs in the annual budget either way.
Cloud costs continue to fall, as long as you are committing to a vendor you believe will remain price competitive and will pass future savings to their customers, you are future proofed to a greater extent. The leading cloud computing vendors also don’t tend to have contractual lock-in periods, you can simply reduce your usage at any time, with no commercial restrictions. So cloud vendor lock-in usually isn’t an issue.
It’s important companies understand the value (and cost savings) cloud vendor native services bring – the goal of a cloud vendor is to make the lives of developers and platform engineers easier, services are highly available, resilient and offer easily configurable security controls such as enabling encryption at rest. If you choose a vendor who is cheaper but provides fewer services, you will introduce additional time and complexity for engineers. This carries a hidden cost in both delivery time and end-product quality, and ultimately your engineers will spend less time building new features and more time wrestling with infrastructure and process.
There are considerable advantages to picking a single cloud vendor rather than diversifying across multiple vendors within your organisation:
• close integration of services providing a better user experience
• the ability to reuse common patterns and components across services
• a shared security and monitoring approach backed by mature management tools
• consolidated billing or management across the organisation
Creating a highly available, secure and cost effective platform on a single cloud provider is hard, creating it across many vendors stretches the time and investment in all aspects.
Also, don’t forget there are significant differences between cloud solutions, you’ll need to find engineers who are specialists with each vendor you select. Highly skilled cloud engineers are hard to find for the more popular cloud vendors, it’s difficult to find expert engineers for some of the less popular cloud vendors, and almost impossible to find engineers with deep knowledge and experience across vendors.
From personal experience, I know that while it’s absolutely possible to build services which are cloud agnostic, it will take double if not triple the development time, code will be more difficult to maintain and you will lose all of the benefits provided by your cloud computing vendor of choice (quite often needing to choose suboptimal alternative solutions in order to maintain independence).
The cost of migrating to a new cloud vendor at some point in the future is far less than the cost of building and maintaining cloud agnostic code for multiple years. It’s absolutely possible your cloud vendor will raise prices such that you’re paying more than you would with an alternative, but is the annual cost difference less than the cost and impact of migrating?
Typically, you’re not locked in by the cloud vendor, you’re locked in by the connections you’ve built to other third party systems (who may not be able to change at the same pace your own teams can – how easy will it be to have them change if you want to migrate?).
Want to find out more? Take a look at our AWS Migration Services here.
There is the risk that a cloud vendor data centre could go down, while the leading vendors are constantly adding failure mitigation into their data centres it’s still possible. With AWS, you have the option to mandate a specific geographic region (which will have its own backup and recovery capability) however it’s also possible to build a failover solution in a different region or availability zone – we recommend this approach for any customers who need to keep their services running 24*7.
There is risk in the fact that AWS currently dominate the cloud industry. Circa 50% of companies use AWS as their cloud vendor (depending on whose statistics you believe). So what happens if AWS goes out of business or suffers a major security breach?
Clearly private cloud vendors are attractive for cybercriminals because if compromised they would hopefully get access to many customers. Take time to understand the security controls cloud service providers have in place and make sure you compare “like for like” as part of your selection process. Of course, the reputation and safety of all cloud vendors is critical for their business. You can be sure they are all taking security seriously, in fact it’s highly likely the security practices of the leading cloud vendors are better than those in your own data centre.
Moving to cloud is not an excuse to lower security standards or assume security is entirely the responsibility of the cloud computing vendor. It’s unlikely (not impossible) that a cloud vendor could be breached however, it’s your responsibility to ensure your applications and data are effectively secured within the cloud such that if that happened the data in your systems would be safe. Ultimately, it’s more likely your systems would be breached but contingency plans and exit strategies form an important part of any organisations cloud strategy.
Digital Dimensions can explain how to architect secure applications within the cloud, contact us about our AWS Security Services.
Digital Dimensions recommends choosing a single cloud vendor and not building a vendor agnostic platform. However, choosing your preferred cloud vendor is the first step. Next, you need to build a single platform for your organisation with the appropriate standards and controls to ensure the security and maintainability of your systems is consistent – that’s where we can help.
We’ve already created large scale, global cloud AWS Platforms for organisations which have helped them control costs, set common standards and security controls and ultimately make better use of cloud technology. Contact us to find out more about AWS and cloud vendor lock-in.
Greenfield is simple and frankly you should ONLY be considering an agile approach because it provides early validation that your service works and there are customers who want…