As was recently announced, Railo, the open source CF engine, has finally given ColdFusion to the masses.  March 31st saw the release of the first 3.1 public beta, providing full feature compliance with Adobe’s ColdFusion 8 standard, and allowing developers to begin porting over existing sites to Railo.  The ability to port over existing sites, or to spin up entire servers for a client without running into the pesky licensing costs of ColdFusion is one of the developments that has me the most excited about Railo.

Previous versions of Railo (including the promising but ultimately not CF8-compliant and buggy 3.0) have been known to provide phenomenal speed increases, but without the ability to fully support the CF standard there have been compatibility issues with web software firms attempting to make a move to Railo.  This, combined with a lack of true enterprise capabilities led many to dub the platform unready for prime time.  Railo 3.1 is about to change all of that, at least once it is finally out of beta.

I have not yet had time to play with Railo 3.1 too much, but they provide an express install that isn’t really an install, so it has been very easy.  Just extract to a folder, double click the ’start’ script to start the application/web server, and then you can immediately browse to it at http://localhost:8888.  Drop code into the Railo webroot folder, and you can start testing existing apps against Railo.  The administrator for Railo 3.0 was very sparse compared to the CF administrator that ColdFusion developers know and love.  Not so with Railo 3.1.  The server adminstrator which manages the more global settings has a separate password from the web administrator, and there are numerous settings available, many specifically tailored towards compatibility with CF8, but there are also enhancements beyond what Adobe provides. Additional enhanced selections within the administrator, such as “convert 0000-00-00 MySQL dates to NULL” seem like a sensible upgrade to the default behavior of CF, others probably depend on the needs of your application.  Missing at this point in the release is the much ballyhooed cfvideo tag, a cluster scope (though Railo supports J2EE sessions at this point), and clustered caching.  With a CF license costs no longer at issue, expect Railo’s clustering functionality to get a full workout in the coming months.

Installing extensions, and restarting the cf service are available within the administrator as well.  Things like Galleon forums, the Mach-II framework, and other open source CF goodies.  Additional providers can be added via the server, too, (this works very similarly to how plugin providers are added via the Eclipse IDE) and updating the server software is also possible within the Railo admin itself.  One of the weirdest things for anyone that has restarted a ColdFusion service before is that Railo’s cf restart is darned-near instantaneous.  Everyone gets logged out on the server, as sessions and other scopes are cleared, but other than that, there is no painful delay waiting for the service to kick in while site visitors are crashing into technical looking 500 server error screens as is so often the case with a typical ColdFusion restart.  It’s…eerie.  It is also a distinct improvement, but performance has always been Railo’s most promising and consistent offering in their platform.

You can bet that many people across the internets have been tinkering with Railo 3.1 lately, especially in tandem with Amazon’s EC2 or similar cloud service, in order to provide things like open source load-balanced J2EE session-scoped cluster farms.  Suddenly, stunningly, ColdFusion developers are now enjoying something that PHP developers have been able to enjoy for years.  I welcome an open CF8 standard (whether Adobe has created or simply joined the CF standard is unclear) and a fully-featured open source ColdFusion application server.  It is clear that this can only mean good things for CFML and ColdFusion developers in the future.

What is not so clear, however, is how Railo’s other open source competitor Blue Dragon has fared, but with many members of the Blue Dragon team leaving (and some of them joining the Railo team), chances are that it will not fare very well.  Equally unclear is Adobe’s opinion on Railo, and how its official release might come to affect its bottom line.  Whatever the case, the cat is out of the bag now.  We’ve seen the future, and the future is open source.

Viva la Revolucion!