We are all told that the cloud will be a cure for our problems. Cheaper, faster and better. You may be considering the cloud too. “But how would I actually implement it at my company?” – you may ask.
I know that the decision is difficult. For that reason, I wrote this article. I will tell you the 7 things you MUST know when considering cloud. Want to choose wisely? Read carefully!
This post has originally been published on Jul 26, 2018. It has since been updated for better readability.
Here you can watch a video summarizing the key takeaways from this article:
Some people are going even further and skipped it altogether. Now it is all about AI, the blockchain, and virtual reality.
There are so many new technologies and features that you don’t even notice them around you. You don’t know how others can keep up with the changes and how they apply them to their business.
Don’t worry! You are not. Many organizations are still exploring and evaluating new technology. They’re struggling with the same things as you are.
I decided to put my CTO hat on and share with you 7 things I’ve learned the hard way about the current state of cloud and organizations. They are based on working with dozens of our customers around the world but also speaking with peers and experts from other companies.
Have you already adopted the cloud at your company? If yes – keep reading. Even just scan it and then share your opinion. Were you following the same directions when considering the cloud? That knowledge may be very important for others.
To make this article even more useful, I will also share some practical steps you should take within your business to get ready. Changes are coming, so be prepared.
You may hear that everyone is doing cloud, but you haven’t yet made the move. Your organization needs to get started but there are tons of projects to take care of, and you don’t know if it is even worth considering.
Suddenly, someone complains about the performance of your e-commerce site. Or the cost of running the document management system. Perfect! You’ve heard that cloud will solve it: cheaper, faster, better. Containers are the solution for everything! Let’s jump on that!
You have just defined the perfect recipe for disaster and put the cloud project on hold for the next year.
If you’re new to the cloud, don’t hop on the train with your most significant cargo on the first trip.
There are at least several vital ingredients for success missing. You won’t yet know:
Should you stop and do nothing? No! You just need to choose a smaller project. Don’t try to learn on your biggest or most critical business system.
There are plenty of opportunities for trying out the cloud, for example:
Your marketing department needs to run a short campaign. They require a way to host landing pages and to communicate with users over different channels including mobile messaging. You can use something like Azure App Services, Logic Apps, a security service such as Azure AD B2C and services like Twilio and build a PoC of it!
One of your servers is ending its life. You need to replace it. Wait! Maybe you can move it to the Azure IaaS, and in the process:
You’re wondering how to provide backup and disaster recovery capabilities for your organization. Azure Backup and Site Recovery is something which might help you here. Evaluate it.
By the way: are you wondering what to do with old Windows 2008 systems still running and going out of support? You can extend your support window by moving them to IaaS and then think about how to upgrade them.
In an excellent book, Ahead in the cloud, I read about the superb rule of 2 weeks. The premise is, if you need to migrate something on-premises to different hardware or data center, see if you can move it to the cloud or re-write/ re-configure it to another service within two weeks.
If the answer is yes: Do it!
It sounds good: our first project. But we don’t know the cloud. Let’s hire someone who does and will teach us.
Here’s some hard truth: there is not that much talent with real skills in the cloud out there.
Many try it, many play with it, but still, people with actual knowledge are not that common. And there’s another aspect to note: the cloud attracts mostly developers and people with mixed skills. They might not be the right choice for your current environment.
But here’s the twist – you already have the right people. They are working for you right now. Specialists who know your organization and your operations. Your employees, analysts.
You want to have the best cloud engineers for your company: grow them. And you will also keep them for years as they will have an exciting job.
Start your “Cloud Center of Excellence”. Don’t make it big.
Here is the recipe for a quick start:
Hey! You’ve just put together your first cloud team. Now, give them the resources to learn:
Now you’re on your way to building your dream team and long-term, satisfied employees at the same time.
What you will hear from vendors and consultants is: cloud is less expensive! Let’s jump on it, save money and revel in it.
You are after your first deployment, moved your primary server to the cloud, and got your first bill. And here comes the question:
Where are my savings?
It is not true that the cloud will always be cheaper in monetary value. A server in the cloud might cost more than your existing hardware. PaaS services in your solution are usage-based. If you use them a lot, there might be a large bill at the end.
The cost-effectiveness of the cloud does not come from direct savings. Instead, it might translate to:
Based on the already mentioned book Ahead, a typical organization might see their costs reduced by 30% but it is expressed in total value, with operations and deployments.
You need to define your definition of cheaper, and you need to measure it. That last thing is important – if you don’t have a way to measure it, how will you know if you are getting there?
Don’t try to figure out some complex system for it. Make it empirical. Find an easy way to capture the current state and track changes and their direction. Things to measure might vary and might cover for instance:
One more thing. This one is important! It is hard to expect things to be better if you keep doing them in the same way. If you want to benefit from cloud deployments, you need to learn to do them in a cloud-appropriate way.
Have you heard the word DevOps? Great! Me too. Too many times in different contexts.
Whatever it means for who is saying it, it is an operating model where you automate your operations and make them part of a process. They’re not separate tasks from development.
The first task for your dream team (see #2): Even if it is a single server they’re deploying, they have to automate that process. It needs to be deployed, configured and operational without manual interaction. Make it a challenge!
Are you following all the vendor announcements? Do you know all the services and improvements?
Every cloud vendor is building more and more services as the demand grows. There are more and more options, services, possibilities.
You look at the videos from the latest Build or AWS:ReInvent, and you think – wow. This is cool. Let’s do this.
Hold your horses! Remember, cloud is a living thing. Vendors build and deploy it on the fly.
If there is a new service and it has a promise of solving your issue, don’t just go ahead and implement it. It might not be what you need. The goal might be harder to achieve than it seems, or it might cost more at your scale than you think it will cost.
Even if a service is serverless and is part of Platform as a Service (PaaS), there are still servers and interfaces behind it. It might have its limits. Or the solution might need some configuration and development.
Not everything you hear from vendors is as perfect as it seems. Don’t accept the solution just as it is. In the end, you will develop, maintain and operate it, even if it is serverless and PaaS.
Think about the support, costs, operations, and deployments.
Nope, but you need to build your process for evaluation and tinkering with it. By now you should have a way of evaluating it:
Keep yourself informed and make the process empirical. Evaluate, build, iterate. It should be your mantra when it comes to cloud services and technologies.
Your people will love this approach.
Do you remember the time when to address a problem we would just buy a product off the shelf? Then it was a never-ending cycle of upgrades and learning of its limitations.
Here’s the hard truth: when it comes to cloud platforms and offerings, there are no products anymore – there are solutions.
Of course, you can buy a SaaS product. You can still buy some products to address the simpler needs.
But when it comes to solving a problem with a cloud platform you will quickly learn that:
That is why your teams should always be cross-functional and why you should expect some development to always happen in your cloud projects.
It is not about deploying ready products. It is about building from active components.
DevOps can be very helpful when it comes to organizing your cloud development processes
Have you heard that “Software is eating the world”? It is true. In our space, what is happening is that “Business is eating IT”.
Sounds like a catchphrase? Yeah, I thought so. Here is an explanation.
Business is faster right now than ever before. Some years ago when your company wanted to deploy a new service, they would come to IT and would ask for it. It would trigger design and procurement processes, hardware purchasing and so on.
You know what will happen right now? If there is a need, your business will find a partner in some consultancy or a development company, use its magic credit card for procurement (yeah, I know it is not that easy), and get it done.
It is. We’ve had a few examples like this ourselves. Business decided to go directly to cloud technology vendors because IT was too slow solving the problem.
There are lots of vendors already doing it for you.
My point here is that if you are in it, you are in the best position to be the business partner for your organization. You don’t have to be afraid of it.
It seems like people didn’t lose their jobs because of the cloud. It is actually the opposite – their number grows if a company embarks on this journey.
What you need to do is learn how to experiment, operate quickly and deliver faster on the business needs. Have you read my previous points? That’s how you get there!
The time will come when you will need to decide where to move. Should you:
I’ve been in a couple of situations where after learning all the options and possible solutions, the customer was stuck, unable to make decisions.
Why? It was not about lack of information or uncertainty about costs. All the data was at hand.
It was inertia caused by the lack of compass – and not asking themselves the right questions.
You need to find out what your objectives really are. For instance:
These are not easy answers to find, and they require some thinking.
A hard fact – no business consultant will tell you what to do. It is you who knows your business and you who has access to all the people with the knowledge of your company goals and directions.
You need to know your direction to make decisions, and not just make them because “others do it this way.”
How to find your direction? It is not easy, and it is a process. But you can take a look at some good content as a starting point.
Keynote: Crossing the River by Feeling the Stones – Simon Wardley, Researcher, Leading Edge Forum.
And here we are! 7 things to note when considering the cloud.
I hope it made for a good read for you. Follow our blog for updates on this topic as we guide you through your cloud journey.
I covered security in GitHub last time. But some of you likely use Azure DevOps for building your products, so let’s t...
Sometimes it feels like I'm pushing too much with security and software development, but then you prove me wrong. Rec...