Yeah, we use the 3-tier approach as well: - Presentation Tier (Webwork/Struts2, JSP, CSS) - Business Tier (Spring) - Data Access Tier (NHibernate) I'll be doing the same thing in the .NET approach (except using Spring.NET and NHibernate instead of their Java counterparts). The reason for the move to .NET is that I find that their set of fuctionality, especially related to the web, is much richer and easier to work with than the JavaEE stack (especially when it comes to Ajax). As far as the licensing issues, it's not a problem. I have an MSDN license through my employer for development, and since the host will provide the OS and the database (SQLServer), the licensing is on their dime. I've found it's actually a little bit cheaper as well to find a .NET host than a JavaEE host. As far as work goes, unfortuantely, the work on the Java version is pretty much halted. All future development will be .NET. If that's something you're interested in, I'm trying to work out a model where contributors can donate code for certain parts of the site. I'm not going to go full open-source with the whole thing, I don't think.