I was on Slashdot and there was actually something I cared to comment about… then I got this.

Then I left.

Rails Hosting

I get a lot of questions about Rails hosting from this blog, so I’ll take a minute to post about some of my experiences.

Site5 Rails Hosting

If you’re looking for hosting for a small website like a typo or mephisto blog Site5 is a great hosting option. I’ve had great luck with them over the last few years. They have a Rails based control panel called backstage which is tied to a customized version of CPanel called SiteAdmin. The engineers at Site5 are Rails guys and they’re always doing some innovative stuff. They also have reseller plans if you need to manage client websites. This blog has been hosted there for a while now and because of that I highly recommend them for Shared Rails hosting.

Slicehost Rails Hosting

When you’re looking for a more dedicated hosting solution for Rails apps Slicehost is the place. You get a virtualized Xen host with the latest stable Ubuntu. They’re perfect for hosting Rails apps that need a little more juice than a shared hosting solution will give you. I’ve had great luck with them in terms of uptime and support. It’s one of those types of places that you just don’t have to worry about once you’ve got an app going. If you’re looking for an excellent Rails hosting environment, especially for development Slicehost is perfect.

Honorable Mentions

I’ve had luck with Rimuhostng in the past. They’re great operation and the support was always really good. They also have an out of the box easy Rails stack install script that makes running a current Rails environment simple.

Non-Starters

I haven’t had a Dreamhost account myself but I have managed an account for a client there and from what I saw the control panel felt hacked, the servers were overbooked and the support wasn’t good. That client switched from them after they wanted more money for a dedicated IP address and more money for support and more money for less value than what other had for the money. I’m sure everyone has heard of the fact that they charged their customers over $7 million after on of the programmers ran a billing script with a bug in it (yikes)!

JSON-P based Comment

Over the last several months I’ve had the pleasure of developer JSON based commenting solutions for publishers. I couldn’t be happier using JSON as a transfer method for moving ActiveRecord based object from the database almost directly to the consumer. I’ve run into some difficulties here and there mainly due to the Same Origin Policy which is a bastard of a browser rule that makes sending JSON across domains difficult. Even though prototype.js seems to support sending requests across domains there is no native script transport in prototype and worse yet it appear some browsers won’t allow AJAX across subdomains to overcome the SOP rules. I searched all over the web and found a few hacks for adding the script tag to prototype.js but I found the best solution was built native into JQuery’s getJSON. I was really taken with JQuery’s ability to handle the script transport method out of the box but I think even more I’m taken with JQuery’s syntax. I had a conversation with Less Everything’s Steven Bristol about 6 months ago and he asked if I had checked out JQuery. I had briefly looked at it but I wasn’t wowed by it (probably because I didn’t use it on a project). Steven: “isn’t it the best thing you’ve ever seen?” Me: It’s ok. (*my answer to everything – ask my wife). Six months later I get to use it on a project and my answer to you Steven is YES it is the greatest.

JSON-P

Back to the subject… So the problem is that a browser doesn’t want to send a request across domains for fear that your secret info will be compromised by some would be hacker. The solution JSON padded with a callback method combined with a plain old script tag aka JSON-P. With JQuery the idea is that you can pass a URL into JQuery’s getJSON method with a ? for JQuery to bind it’s on changing function name that handles a callback. Sound like a hack? Yes but everyone is doing it. I’ve seen some skeptics but overall this is an accepted solution. And until JSONRequest is accepted as a safe cross site transport JSON-P is here to stay.

Does Rails support JSON-P?

Bet your ass it does. Right out of the box Rails supports the callback option to be passed in on a :json render. Like so:

render :json => @comments, :callback => params[:callback]

JSON-P Problems on Rails

So the issue you’ll run into primarily with JQuery is the changing name of the callback. JQuery binds a random function name to the request (presumably to protect from attacks of some sort, maybe for anti caching). The issue is that with action caching caches the entire response body meaning the next call has a stale cache (because of the now changed callback name) or has to generate a new response for a new callback name. While JSON is typically very light weight the to_json method can be expensive and when you’re dealing with high traffic situations you always want to squeeze every bit of performance out that you can. We also do paginated result sets with will_paginate so it means there is a bit of post processing after a plain old find_all_by_blah… The solution I’ve been using is a mix of cache_fu for model level caching along with fragment caching the to_json results then interpolating the cached json into the callback. Sound like a hack? It is but it feels a bit better when you crunch out over 500/reqs/s as opposed to 14/reqs/s.

For the future

Let’s cross our fingers for CouchDB. I’ve been experimenting with Couch over the last week or two and I’m really pleased with the possibility of a RESTful document based database with native JSON and coming support for MapReduce. The future looks bright, I can imagine not so distant support for native ruby object level persistence. Yay!