Tuesday, May 6, 2008
Tuesday, April 8, 2008
Flex and MVC
Is Flex yet another MVC framework like Struts and 100 other java based frameworks? One such framework thinks so and has built complete set of support for actions and controllers for Flex - Gausax at http://www.guasax.com
Force fitting RIA frameworks especially Flex into an MVC misses the whole point and reduces it to UI eye candy. Ajax world is slowly but steadily picking up in rich controls and effects without the overhead of a 300K app download, so the eye candy loses its worth.
Flex is really good at alleviating server load and thus provides better scalability and failover than a regular MVC framework. In theory most web frameworks support building stateless applications (like Google) but that is not the norm. The server side continues to drive the client thus limiting its own scalability. Flex provides a way to push the entire responsibility of UI to the browser so the server becomes a service processing business transactions. It takes no part in the UI handling thus removing the need for an http session. That removes the browser to server affinity and makes servers a lot more scalable. Give a bunch of failover/clustered server urls to the client and client can take care of failover as well load balancing without a SPOF on the server.
To summarize please do use Flex in the way it is supposed to be and you will realize quite a few gains on the server not to mention eyecandy for the user. Who is complaining anyway?
Force fitting RIA frameworks especially Flex into an MVC misses the whole point and reduces it to UI eye candy. Ajax world is slowly but steadily picking up in rich controls and effects without the overhead of a 300K app download, so the eye candy loses its worth.
Flex is really good at alleviating server load and thus provides better scalability and failover than a regular MVC framework. In theory most web frameworks support building stateless applications (like Google) but that is not the norm. The server side continues to drive the client thus limiting its own scalability. Flex provides a way to push the entire responsibility of UI to the browser so the server becomes a service processing business transactions. It takes no part in the UI handling thus removing the need for an http session. That removes the browser to server affinity and makes servers a lot more scalable. Give a bunch of failover/clustered server urls to the client and client can take care of failover as well load balancing without a SPOF on the server.
To summarize please do use Flex in the way it is supposed to be and you will realize quite a few gains on the server not to mention eyecandy for the user. Who is complaining anyway?
Subscribe to:
Posts (Atom)
