Everytime I read another post about the simplicity and affordability of moving to Rails I go hmm; this time I’m going HMMMMM!
InfoQ: Architecting TekPub – Moving from ASP.NET MVC to Ruby on Rails.
One of my clients business is audio sales via cd-burning and downloading through retail kiosks as well as remote fulfillment via web orders (phew – say that four times fast). It is an interesting business that I’ve been working with for 4.5 years. Besides the content role I’ve had that included CDN management, transcoding, SAN management, audio ingestion, database strategies and what not I’ve recently inherited an ASP.NET site. The site is receiving more business support and our team is working to add features, do a redesign and I’m also doing little tweaks that will help spruce up its performance.
The first item on my list was to implement compression on the site. The web server hasn’t been upgraded to IIS7 yet and I’ve long forgotten how to use compression with IIS6. The best resource I found was Scott Forsyth’s post on it (IIS Compression in IIS6.0 – Scott Forsyth’s Blog – thanks Scott). One item I didn’t do on the first implementation was add js and css files into the static file list so I’ll be doing that as well.
Up next is introducing URL rerouting to deal with dynamic content. I just have a hunch that using domain.com/artist/beyonce will be better than domain.com/artist.aspx?artistguid=dkfjdsfkjf. That obviously relates to SEO and after the URL rerouting is in place we’ll go through the results of a IIS SEO Toolkit examination as well as combing through the YSlow results.
A redesign is coming as well and I wish I there was a reason to convert it to a MVC app but it just doesn’t seem prudent.
Today I came across a .Net developer survey put on by Matt Berseth. Matt’s survey is focused on developers’ usage of social networking which has me interested to see the results. I’d love to see a lot of responses on this one so if you are a .Net developer do a data pledge!
