Rob Brooks-Bilson
Tech, Photography, Stuff
Positioning ColdFusion in the Enterprise
January 4, 2007
Back in August, Tim Buntel posted a short presentation titled 5 Reasons to use ColdFusion for your next internet application project. The presentation was designed to give ColdFusion developers and evangelists something they could present to their management and/or clients to make the case for ColdFusion.
In the presentation, the top five reasons given are:
- Increased Productivity
- Standard J2EE Environment
- Innovative Features
- Integration with other Adobe products
- Part of a world-class software company
What I'd like to know is how other developers/managers out there sell/position/defend ColdFusion within their organizations? Are you using these same reasons? How are you expanding on them, and what else are you including?
Beyond that, I'd like to know how many other corporate developers out there are using ColdFusion in a mixed environment with other languages such as Java, .Net, etc. If you are in a mixed environment, what % of your development is in ColdFusion vs. the other language(s).
TweetBacks
1/5/07 12:30 PM
CF is super easy to learn and is a very powerful web development tool. The CF community is great, too. We use it for 100% of our web application development (State of Oregon, DCBS). I can't think of any project that someone has proposed where we thought "ColdFusion can't do that".
1/5/07 5:37 PM
How about "we have several other successful apps written in ColdFusion"? I guess CF has to exist at the organization first, but I have heard a lot of stories of management trying to "standardize" their many platforms, and CF has had to compete with Java, .NET, etc. I have observed some large shops (IE government) where multi-year java projects failed to get off the ground, while the CF team kept cranking out apps of equal or greater size. A proven record is always a good argument!
Also, "our existing staff knows CF". Again, it seems that many times someone up top hears that "Java is the (only) Enterprise option" or ".Net is the next big thing" and wants a case for keeping CF around. But changing platforms can at best cause a slow down due to the learning curve and migration process, and at worst result in the turnover of the entire team. I guess if you want everyone to quit maybe that could be a way to do it ;)
1/12/07 2:09 PM
I always point out that Cold Fusion is superior for web apps because it was designed for the web whereas Java and .NET were not.
One way to prove your point is have a "race" between a CF, Java, and .NET developer to get a web app up and running from scratch. The CF developer will win everytime and probably have a superior product.
9/28/07 2:59 AM
cool..