Using ColdFusion frameworks

Question

Can someone state the flaws, if any, to use the ColdFusion development infrastructure? I have been developing the application traditionally, and I am tempted to use the framework after seeing how simple things can be done.

I am new to ColdFusion and frameworks in general. I want to understand the implications of using a structure, including the advantages and disadvantages.

Answer 1

Disadvantages:

• learning curve (select a reduced structure to reduce this)
• the front controller makes an ugly URL, often requiring a rewrite of the URLs at the web server level.
• split risk ceases (no support, hard to maintain, breaking new CF ver)
• frameworks (choose a popular structure with good and fast support)
• it’s harder to debug sometimes, since actions are usually no longer .cfm. Tip: use cfdump and cfabort to see the dump in the controller layer.
• Some structures take longer to reuse. Since most frameworks cache configurations and the level of the controller to improve performance, you need to be constantly updated during the development phase. CF9 alleviates this problem because it is much faster.
• Finally, sometimes you will use the API framework, an abstraction from CFML, and skip your own ColdFusion method to solve the same problem.

Performance is usually not a problem. Do not worry.

Answer 2

Henry has already given a good answer, but I would just like to pick up this part of your question:

But isn't this a performance tax?

The overhead of structure performance is negligible.

In fact, you can even get better performance from frameworks like ColdBox that have built-in caching.

Remember that most frameworks are mature codebases used by a lot of people - most likely, your new unverified code will be the culprit, not the framework.

However, as a general rule (not specific to frameworks), performance is not a problem unless you have measurable results that say it is .

i.e. don't just think: “I'm going to make X instead of Y because I think it will be faster” - go with the simplest option that meets the needs of users, and only change it if you can prove that it has performance problems and that your proposed solution is better.

Answer 3

It depends on the nature of the project. I believe that it is always recommended to use a framework for better code organization, scalability, conventions and others. If you have to start with an enterprise application, then Coldbox is the best structure as far as I can tell. It has a wider learning curve, but its training value. If its a simple project launch, then FW1 is good. Here you can find the list

http://www.riaxe.com/blog/top-coldfusion-frameworks/