What are the advantages and disadvantages between action based and component based frameworks?

14

Regardless of the framework or language (php, java, c #)

What are the main advantages and disadvantages between action based and component based frameworks?

In what environment does one or the other fit best? Which one type of application tends to be better than the other?

Examples of applications if you can.

    
asked by anonymous 22.04.2014 / 19:37

2 answers

15

According to some research I've done, here are some points to analyze, everything depends on the need of your software:

Action based

  • Who uses this approach: VRaptor, Struts 2, WebWork, Grails / GSP, Play, Spring Web MVC

  • Easy to perform tests; ;

  • Provides better code maintenance;

  • You need knowledge in HTML, CSS and JavaScript.

Component based

  • Ready-to-use components;

  • Difficult to make customizations;

  • Difficult to perform tests;

  • Invokes the developer to mix the MVC layers;

  • Consume more memory;

  • Abstracts using HTML, CSS and JavaScript

  

I suggest you read this article (link below) where it addresses the   citing some examples in practice using the language   Java.   
link

OBS: I am a C # programmer.

    
24.04.2014 / 21:49
1

What would be interesting is the combination of these two paradigms, which is what Crux Framework allows us through GWT. With it, we have an Action Based (MVC Push) since HTTP requests are directed exclusively to the handling of business rules and not front controller interface rules (which in this case is allocated in the client). At the same time, we have a Component Based (MVC Pull) because the front controller code is written in Java, the pages are xHTML resources (which can contain pure HTML elements) and are built through components. In terms of advantages and disadvantages, our friend Gustavuu responded very well. In addition, I give a read link .

    
11.09.2014 / 01:22