Introduction
A few months ago I decided to move away from Linode VPS instance over to CloudWays. If you recall my previous blog post from a few years back I moved the hosting of this site over to a Linode VPS. My reasoning behind this is to allow me to try and focus more on building websites instead of managing the server. Whilst this site is small and the server only required a small bit of debugging I decided to give up the extra freedom a custom server offered in favour of a simpler, less time consuming solution.
Why I decided to Move
As touched on in the above paragraph I wanted to focus more on building websites, apps and creating more content for this blog. Whilst I could have left the other server with unattended upgrades and left it at that. I was drawn more towards another solution which wasn't too expensive but the platform gave me a few extra features.
With a young family I no longer found the time or interest to start tweaking configuration files and managing package updates and server upgrades.
Why Cloudways?
Cloudways seemed like a pretty good solution and what sold it was the backup and restore functionality as well as the performance benefits provided by using Varnish etc right out of the box. I've been tinkering with servers since I started my first agency job back in 2012 and whilst I enjoyed it back then, it's just not something that excites me as much at the moment.
I've heard great things from others about how easy Cloudways is to get up and running and having that extra live chat support when trying to fix issues is really helpful.
Conclusion: How is CloudWays?
After using Cloudways for a few months I can happily say that I haven't had any hiccups at all with the service. There have been a few teething problems but this will be the case when moving from a VPS over to a more restrictive, managed solution.
