Clever Geek Handbook

Is there a real need for a server side architecture for an RIA application?

Do we really need a server side architecture to build an RIA application?

My idea is this:

  • Build a complete RIA application using only Html pages, jQuery, and a full set of client side UI components (choose a venom between the many different components available open source, not)
  • Server side I only have one or more RESTs like web services that return and accept serialized Json objects.

No longer reliant on the latest trend in server side architecture (Struts, Java faces, Asp.Net, MVC, or any other model that was once trendy or trendy now), the web server side will just be an interface between trasnsport (Json ) and the business logic layer, there is very little logic in it.

On the client side, we will have a huge JavaScript application, but with modern browsers and computers (for speed) and a modern development environment for easier maintenance (VS2008 and other tools are very good at debugging JavaScript). I see fewer problems maintaining the code for this layer than finding a developer who knows the correct server layer architecture ...

Do you have a comment on this scenario?

Ciao massimo

+1


source to share


4 answers


You could easily ask how to implement a top-notch backend by getting the server side right while avoiding the latest fancy client quirk. And I think that would be a legitimate target anyway. You don't mention if this is a pre-existing application, but if it is, then I would say first skip past Fowler's book Refactoring and then go.



Much churn in software is useful if you know how to properly apply what you need to know to achieve your client-side goals, because the same concepts (SOC, communication-vs-cohesion, DRY, YAGNI, etc.) are applied to both ends, and we increasingly have useful tools at hand to apply them (which can be achieved more or less easily with a variety of technologies.)

+1


source


Just don't put client side security logic ...; -)



+1


source


Or don't even bother with the REST / Json part and use something like DWR to talk directly from your client side code to the POJO server.

0


source


Most RIA applications do not require MVC or component infrastructure as C, V and most M are on the client. However, you still need some kind of service level to interact with the client, as well as a persistence level to work with the database.

0


source






More articles:


All Articles