The night before I left to travel for the holidays, I was very excited to receive my beta invite for Liquidweb’s new cloud hosting platform, Storm on Demand. I have been in the beta invite queue since Liquidweb first announced this new venture. To say the least, my excitement has not yet been let down.
Since I first signed up, I’ve been able to play with everything and the best way I can describe it is it’s a mix between Rackspace cloud and Amazon EC2. Liquidweb strongly pushes their support and service as does Rackspace and also include a backup feature but have also taken note on VPS’s CPU and memory and bandwidth pricing from Amazon. Then of course, they have thrown a few features of their own in too.
These are some of the features I’ve run into so far:
When a instance is created it basically is assigned certain number of CPU’s based on the size of the instance. Each virtual CPU is a 2.2ghz Xeon. They don’t advertise this on the Storm on Demand front page, but is displayed when you create a new instance. 2gb instance has 1 VCPU, 4gb 2 VCPU’s, 8gb 4 VCPU’s, 16gb 4 VCPU’s, 32gb 8 VCPU’s.
The control panel is very slick and responsive.
No host is perfect, so I want to talk about some of the downsides I’ve run into so far.
Major Issues:
Minor things:
Overall impression
I’m always excited to see new hosting technologies come out and see what competitors come up with next. I think Storm’s big advantages are their price’s of larger instances and the ease of use of some key features such as backups and creating server images. I’m also excited to see what their API is going to look like. My biggest peeve of Storm so far is why I was billed $38 for something that I’m suppose to pay for only what I use by the hour.
Aside from a chat client, Skype is a great solution if you are looking to have another line. Currently I use my skype number as my office phone. At 3$/mo for unlimited calls, it is a steal. I have been shopping around for a good skype phone for a long while now and I have finally found one. The IPEVO S0-10W Wifi desktop skype phone. I have been using this for a few days now and it is great.
The phone features speed dial settings, 3 dedicated speed dial buttons, speaker phone, wifi capable, and a whole slew of other features. This phone is a nice compact size yet feels very sturdy when handling it. The buttons feel nice when you press them. You feel like you have really accomplished something while dialing a number. When I first pulled htis out of the box and plugged it in I was able to set it up in minutes. All I had to do was set the date and time and then sign in with my skype account. It will also automatically check for firmware updates, no need for a computer, completely indedpendent. Any settings you can set in the desktop skype client you can set on this phone (even your skype status and note).
Overall I am very happy with this phone. You can find this through IPEVO’s website.
Update: I just noticed that the base/handset has magnets in them to keep the handset on the base, very cool.
S3 is Amazon web service’s cloud storage solution offering very cheap price-per-gb storage and bandwidth which makes this a very cost effective backup solution. Currently I use JungleDisk for mounting S3 buckets as drives and to schedule backups, and s3sync to backup my files in various unix enviroments but I dont have anything in between to where I can easily manage my S3 files. That is where Cloudberry Explorer for Amazon S3 comes in. I have been using this for the past couple of hours or so and to say the least I am impressed.
Here is what I’ve noticed while using Cloudberry. 
Though through using this there are a couple things that could be added that would be nice.
Overall, this is a pretty solid S3 client and I plan to keep on using it.
A couple months back I signed up for the GoDadddy Grid Host beta. It was too great of a deal to pass up, 5$/mo with 100gb of space and 1TB of bandwidth (basically what MediaTemple gives you).
For this review I set up a test blog that syndicated around 20 different feeds. 37k posts and 2.7k comments later, I think I have a good base site to test this service with.
It has been 4 months, and so far my impression is “meh”. It seems to be plagued with the common problems that all grid hosting is struck with, one being mysql as the bottle neck. Everything I ran that did not require a database back end was lightning fast, significantly faster than any shared host out there.
Here are the results of a benchmark I ran using a script that would test strings, dates, file system i/o, encryption, dates, images, arrays, and objects.
As shown above, godaddy is much faster, by 250ms and other users should not affect the processing power unlike a shared host where everyone is competing for the same cpu cycles. But like i said above, the bottleneck wasn’t with the actual running of website scripts, it was the database. My test blog is terribly slow when caching is not enabled, but once I did enable caching, load times dropped significantly. With a lot of grid systems, they do not scale mysql like they do web servers.
Another common “feature” with grid hosting is better uptime, that doesn’t seem to be the case with godaddy. I used pingdom to monitor my test blog and within 4 months, I accumulated a total of 14 hours 27 minutes of downtime which brought my uptime(%) to 99.29%, far from godaddy’s claimed “99.9%”.
Compare to these uptime statistics to my current host uptime with only 40m down, 99.97% up since november of 2008.
In all fairness, this service is still in beta and grid systems do take a while to get all the kinks worked out (MediaTemple being a prime example) but currently the downtime is unacceptable so I suggest avoiding it for now.
If you are looking for a good host, I suggest slicehost or linode for a VPS, dreamhost if you want a billion features, or lunarpages if you like cpanel and want things stable.
I swear, every single web host that ever existed provides the same old basic webmail platforms, either SquirrelMail, Horde, or both. Now don’t get me wrong, these two webmail platforms are very reliable and secure and have been around for a long time now, but they just feel really outdated and only come with standard features.
But if you are like me, you don’t want your eyeballs to bleed every time you need to read you webmail and a slick interface and some AJAX thrown in definitely wouldn’t hurt.
Pros:
Cons:
Pros:
Cons:
Pros
Cons:
I noticed there something that all these clients including SquirrelMail don’t include that Horde does, and that is a calendar. Which to me, is really no big whoop, but it might be for others. If there there is important date or appointment I need to remember, I prefer to use Google Calendar, or I can put it in my phone, or my work calendar.
After trying out all these clients, I decided to go with roundcube for my brontesaurus email.