Why Cairngorm? Why Not PureMVC

Hello Friends,

Quite often people asked me why Cairngorm? Why not PureMVC? Which is best?

My answere is that both are having some pros and cons so that would be a trade off. The best way is to understand the requirement of your project and then choose a particular framework. If you feel, both of them are not a best suit in your project then, you can just choose to extend one as per your requirement.

Here I compiled few points which I guess enough to justify why Cairngorm!! It also give you an idea of where you can use pure MVC

• Cairngorm is a refined form of MVC pattern and is highly customized for medium to high complex flex projects. It takes advantages of native flex features such as binding. In comparison PureMVC is a more generic and isn't developed keeping in mind of any particular technologies so unable to leverage native flex features.

• Cairngorm is a lot easier to learn than PureMVC and at least it delivers on the promise to let people quickly get up to the speed on large projects.

• It is developed and used by Adobe Consulting, "The developer of Flex SDK". So while developing Cairngorm, they implemented the best practices to achieve maximum out of the flex SDK using a framework.

• Cairngorm is Enterprise-Oriented and PureMVC is User Interface oriented. So, If an application that has a rich User Interface then the best choice is PureMVC, but if you rely a lot on a DB server and need to make many calls to get data from server, then Cairngorm is the best choice.

• It is widely accepted in the flex developer community and probably most developers are familiar with it.

• Cairngorm helps on large application breaking it in smaller pieces (classes), adding strength, reusability and flexibility. One wouldn't able to take much advantage of Cairngorm on small applications from the simple fact that the framework doesn't have room to express itself.

Thanks,

Shaleen Jain