Channels ▼
RSS

Tools

Server+client Fusion: An Architectural Proposal


Server+client Fusion: An Architectural Proposal

The solution sounds easy. To obtain the benefits of both architectures why not combine them? While this is an easy statement to make it is not as easy to implement. To make the union work a lot of technologies need to be integrated. For example most people do not just start writing JavaScript at the client. Many use a snippet framework such as jQuery.

For a developer wanting to combine snippet frameworks such as jQuery and larger frameworks this can cause integration problems. Therefore it is best for one package to provide the Server+client Fusion architecture out of the box.

This is where Server+client Fusion steps up to the plate. The concept was first introduced by ZK 5, which is a Java-based Ajax framework. ZK's mantra is that it is "developer-centric" as it provides the developers the ability to create their applications quickly using Server-centric architecture then optimize them using client-side constructs. See Figure 3.

Figure 3: Server+client Fusion

There are two advantages to this approach:

  • Provides all the advantages of server-centric and client-centric approaches
  • Provides none of the disadvantages

Server+client Fusion provides developers and architects with a choice of implementation. A good framework architecture is flexible empowering developers and architects to implement their applications in a smart and elegant manner.

Real-world Use

In most real-world situations you will want to build the initial application quickly and effectively using server-centric technology, and then introduce client-side optimizations. This is where Server+client Fusion architecture comes in to its own. For example, when implementing auto-completion functionality, you can preload data improving response time.

Normally productivity and optimization using client-side techniques do not go hand in hand due to Granularity issues. However, ZK has a base which takes care of server-centric granularity issues by applying a batch processing model to deal with emergent and deferrable requests. With Server+client Fusion, developers have a choice to further optimize the granularity based on an application's requirements.

Conclusion

Server+client Fusion will aid in the development of large scale web applications which are now coming to the fore due to the advent of cloud computing. Cloud computing is driving a trend for more innovation in web development with the goal to produce web applications in the quickest and most efficient manner possible.

For More Information

Staten, James, et al. Is Cloud Computing Ready For The Enterprise? March 7, 2008.

Linthicum, David. Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide . s.l. : Addison-Wesley Professional, 2009. 978-0136009221.

Chen, Henri and Cheng, Robbie. ZK: Ajax without the Javascript Framework. s.l. : Apress, 2007. 978-1590599013.

Cheng, Robbie. How to Choose an RIA Solution. Ajax World. [Online] December 30, 2008. http://ajax.sys-con.com/node/781133.

Gupta, Vipul. Accelerated GWT: Building Enterprise Google Web Toolkit Applications. s.l. : Apress, 2008. B001PBEW34.

Katz, Yehuda, Resig, John and Bear, Bibeault. jQuery in Action. s.l. : Manning Publications, 2008. 978-1933988351.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video