[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2659) more friendly documentation
Pete Muir (JIRA)
jira-events at lists.jboss.org
Tue Mar 11 08:52:58 EDT 2008
[ http://jira.jboss.com/jira/browse/JBSEAM-2659?page=all ]
Pete Muir closed JBSEAM-2659.
I like it how it is.
> more friendly documentation
> Key: JBSEAM-2659
> URL: http://jira.jboss.com/jira/browse/JBSEAM-2659
> Project: JBoss Seam
> Issue Type: Task
> Components: Documentation Issues
> Affects Versions: 2.0.1.GA, 2.0.0.GA
> Environment: any
> Reporter: Sebastian Hennebrueder
> Priority: Minor
> I would propose a more friendly formulation in the documentation. See my mail on the developer mailinglist
> existing 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 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. Of course, sharing
> the database is the primary problem with scaling a multi-user application?so the claim that this architecture is
> highly scalable is absurd, and tells you a lot about the kind of applications that these folks spend most of their
> time working on.
> 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.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues