ColdFusion in an Enterprise Environment - Part 2 - Choosing ColdBox
There is many reasons I have picked coldbox over other CF frameworks, but I don't want this to get into why, should I, or you idiot you shouldn't of picked coldbox because -x- framework is better. Rather, I'd rather explain how I are using the framework to make development easier with an office of developers. The following are seven of the reasons I choose coldbox
1.) ColdBox.org provides a lot of great documentation, and almost overstates the amount of documentation. It does have a lot of great documentation, especially some of its competitors. But some of the documentation is not layed out well for someone jumping into a framework. But this is one of the reasons I choose coldbox.
2.) Provides MVC!!!! And it provides it by forcing you to code. Providing you the most powerful MVC capabilities, not wrapped into AOP, forcing a developer to design it out before he just starts coding and expecting the framework to do it for him/her. Sorry this was a little strong opinionated, I see the need for AOP framework, but not for every application. Which leads to another reason I choose coldbox over the others.
3.) Coldbox plays well with other frameworks. Providing you the ability to do less SQL coding using transfer (assuming it is a good business decision), providing you the ability to do injection processing when needed using many different frameworks.
4.) Convention… nice and clean… I let you read about it here http://ortus.svnrepository.com/coldbox/trac.cgi/wiki/cbDirectoryStructure
5.) Integration into UNIT testing frameworks like MXUNIT.
6.) Integration into my favorite IDE… eclipse.
7.) Other advanced features I have yet to get into yet. Like plugins and interceptors..
Please Note: This post is conjuction with a series of blog posts about my findings in setting up an enterprise development environment. Please view the rest of the posts at Coldfusion in an Enterprise Overview
Comments
Post a Comment