I love AWS, but the way my company works, we often find ourselves in a position where we have to pass hosting costs through to the client, and Amazon doesn’t give you any basic utility in the console to do just that.
Okay, the cloud (or grid or whatever they’re calling it now) isn’t exactly a lie, but at least on a retail level, it hasn’t held up to the hype.
Continuing in the Moving to Mosso series, I’ve come across a few more issues that anyone considering moving to Mosso should consider.
It’s been over a month since I opened my account with Mosso, Rackspace’s cloud hosting division. Overall, I’ve been very happy with my decision – but there are a few things you may want to be aware of if you’re considering switching.
I am in the process of migrating all 200 domain names (approximately 100 websites) on my server over to Mosso – which is why you would have gotten a 404 if you happened on the site for a short time last night. (.htaccess did not transfer correctly, so mod_rewrites were
Its a call you never, ever want to get. “My server is down!” or “Our website has been hacked!” As a developer, there are few things that make you look worse than getting a call from your client letting you know that their site is down, or worse yet, hacked.