We moved to AWS.
Until then, my site was down with customers complaining to me.
AWS will expect you to do the same thing but it'll be much harder just because it's AWS.
It is my opinion that killing public access to a paying customer's server without talking to them first, and not providing any remedy for 60+ hours, is definitely something that DO support deserves blame for.
>many years ago when we both were young. It was love at first sight – The elegant UI, the ease of use, the dirt-cheap price was everything I was looking for in a partner.
>There was no downtime, highly reliable as a partner and supported me with every problem I faced in life.
>I understood how to work with her and things to expect from her. Never before had she let me down. It was smooth sailing until recently when problems in our relationship started to surface. She expected more from me and wanted to change me.
Someone really had pampered life -- this does not look like core functionality at all. I'd expect any service to have limitations like those.
If you want to grumble about DO for stuff, their absolutely scattered performance on lower end instances is a better one, though for how cheap the bandwidth is, it can be made to work. And when things like CloudFlare exist, I can't fault DO for not duplicating that sort of behavior.
1. My Saas platform supports custom domains including naked domains and not just subdomains so it is important for me that the IP address remains the same when I add more capacity. I am running a single large droplet as of now and when I tried to add more instance + LB, DO wouldn't let me do that. Several people have asked this feature if you look in their forums. Unless I run and manage my own Haproxy/Nginx boxes, I cannot scale up.
2. This is currently a side project and I do not have additional time to maintain more resources which is why I am willing to spend more on a platform that provides me these features. This is not due to laziness as some people have commented.
Not something I'd expect from someone who has used DO for years.
If the author is look for more affection, I don't think AWS is the route to go. I'd go the other way toward Heroku-like platform. (Oh and shout out to Python Anywhere - great relationship there)
