[seam-dev] Friendly documentation

Gavin King gavin at hibernate.org
Wed Feb 20 20:46:33 EST 2008


Sorry mate, I target my docs to folks with a sense of humor,
who don't take all this techno-religious-war crap too
seriously.

On Wed, Feb 20, 2008 at 11:14 PM, Sebastian Hennebrueder
<usenet at laliluna.de> wrote:
> Hello,
>
>  in chapter 19 (caching) of the seam documentation, there is the
>  following paragraph. In my opinion, it is not at all polite as we call
>  them silly, use expressions like 'will try to tell you' and so on.
>
>  Dealing with other people in that way does not express better technology
>  or better knowledge. I would interprete it as being snobbish, subjectiv
>  and find that it is not very much convincing. Though I know that the
>  core argument is in fact correct.
>
>  May be it is just me being to sensible, but what is your opinion on this.
>
>  Best Regards
>
>  Sebastian Hennebrueder
>
>  -------
>  In almost all enterprise applications, the database is the primary
>  bottleneck, and the least scalable tier of the
>  runtime environment. People from a PHP/Ruby environment will try to tell
>  you that so-called "shared nothing"
>  architectures scale well. While that may be literally true, I don't know
>  of many interesting multi-user applica-
>  tions which can be implemented with no sharing of resources between
>  different nodes of the cluster. What these
>  silly people are really thinking of is a "share nothing except for the
>  database" architecture. ....
>
>  -------------
>  alternative formulation:
>  In almost all enterprise applications, the database is the primary
>  bottleneck, and the least scalable tier of the runtime environment.
>  People from a PHP/Ruby environment state that their lightweigth
>  architecture - which is not sharing resources - scales well. We do not
>  agree here. A PHP/Ruby will share the database which is in large scale
>  application normally already the bottleneck. Lightweight can be fast in
>  smaller applications but is not scalable.
>
>  This chapter explains how Seam uses caching to provide a architecture
>  which is fast and scalable at the same time.
>  _______________________________________________
>  seam-dev mailing list
>  seam-dev at lists.jboss.org
>  https://lists.jboss.org/mailman/listinfo/seam-dev
>



-- 
Gavin King
gavin.king at gmail.com
http://hibernate.org
http://jboss.com/products/seam
http://in.relation.to/Bloggers/Gavin



More information about the seam-dev mailing list