I've to agree. Seeing the software stack, I can definitely point to the database as the most probable candidate for failure. I've been using and managing Postgresql database for a little while (not as much as Oracle) and I can definitely say that features available might not be a best fit for applications like TSS.
My understanding is that if you have to use text search capability, you have to probably use database specific functions and queries that might not be available thru JDBC and that depending on versions of the JDBC driver (and the database), your performance varies. In addition, hearing from Howard's description of the backend schema containing only a handful of tables, you're definitely going to run into bottlenecks because there are only those handful of tables serving thousands of users concurrently. What seems strange is that the decision of using Postgresql (which does not support clustering to load balance) as the backend to support a cluster of app servers seems mysterious to me. Don't misunderstand me, I love Postgresql, and I know its capabilities and limits. And I simply don't think it is appropriate for this kind of loads. Anyway, just me 2 cents. -----Original Message----- From: Konstantin Ignatyev [mailto:[EMAIL PROTECTED] Sent: Friday, September 23, 2005 10:44 AM To: Tapestry users Subject: Re: TheServerSide.com moving away from Tapestry? http://www.theserverside.com/news/thread.tss?thread_id=36654#185568 That IMO says exactly (although indirectly) what does not work and why TSS cannot tell directly what the problem is. --- Benjamin Tomasini <[EMAIL PROTECTED]> wrote: > It *could* get really ugly. But from the tone of > the discussions, it > looks like the TSS folks are taking a very balanced > and honest approach. > > There was one ad hominem post that just listed the > "culprits" without > any kind of logical support. Joseph seemed to take > care of that well. > > The best way to answer any unfounded blame is to ask > for meaningful data > behind any presented analysis. If TSS keeps this > up, I think the > Tapestry community, and the Java community as a > whole will be served > well. I still have faith that the OSS community is > a mertiocracy, and > that over the long run, merit wins out over > marketing and FUD. > > We'll see. > > I did try to post something like this on TSS, but I > couldn't login. :) > > Ben > > Geoff Longman wrote: > > >I understand. It's just that nobody is standing up > for Tapestry and > >you are the only one with enough information to do > that without > >sounding like an idiot. > > > >I realize there's a fine line to tread to avoid > things degenerating > >into fingerpointing. But the way I see it, the > longer TechTarget is > >in trouble the more likely it is that they will > start looking for > >scapegoats. I'm sure the people in there are > working hard to solve the > >problems. But what if another 3 weeks go by without > improvement? I > >would expect at that point the insiders will go > into "save my butt" > >mode and shift blame to anything and everything > they can to save thier > >jobs. > > > >I could get really ugly. > > > >Geoff > > > >On 9/23/05, Howard Lewis Ship <[EMAIL PROTECTED]> > wrote: > > > > > >>These posts about TSS are troubling. > >> > >>The basic issue is that I signed on with The > Middleware Company to do > >>a number of phases of development of > TheServerSide.com. The first > >>phase was the basic translation of the site to a > component object > >>model, leaving all the functionality unchanged. > >> > >>At the same time this was occuring, a seperate > team was converting the > >>backend access from entity EJBs to Solarmetric > Kodo. > >> > >>In the end, I had less than a week to integrate > the two before going > >>live. And yet, for the most part, the result was > quite succesful. > >> > >>However, with the acquisition of The Middleware > Company by Tech > >>Target, my involvement with TSS came to an end; > the later, more > >>interesting phases, where we simplified the stack > and built > >>considerable UI improvements, has not come to > pass. All I've seen is > >>the introduction of more and more ads on the site. > >> > >>I can't talk to the root problem today; I don't > know it ... I do know > >>that Tapestry is doing exactly what its supposed > to be doing, that the > >>functionality problems (missing posts and such) > are a problem at the > >>application layer (the stateless session bean used > to manage > >>transactions) and the interaction between that > layer, Kodo, Coherence, > >>WebLogic and the database. In fact, given the > simplicity of the > >>database schema (just six or eight tables) I > suspect the problem > >>really is in the configuration and integration of > these elements. > >> > >>Based on what I've read, and some high level > discussions I had with > >>them last winter, I believe TechTarget is building > a single enterprise > >>wide solution for all their many web sites., > migrating away from the > >>Tcl-based Vignette solution used by the majority > of their sites, as > >>well as the Tapestry-based solution for TSS.com > and TSS.net. All I > >>know about the solution is that it will be based > on JEE (assuming that > >>hasn't changed since our discussions). > >> > >> > >> > >>On 9/22/05, Matt Welch <[EMAIL PROTECTED]> > wrote: > >> > >> > >>>http://www.theserverside.com/news/thread.tss?thread_id=36654 > >>> > >>>In the above referenced thread there is a > reference to the TSS having some > >>>serious issues with the perfromance and UI of > their site and that they will > >>>soon be moving to an all new codebase. Wasn't it > pretty recently that TSS > >>>relaunched using Tapestry? Are they having > problems with it? I'd be curious > >>>to find out as I'm considering using Tapestry on > a large scale product in > >>>the not to distant future and wouldn't want to > come up against the same > >>>problems. > >>> > >>> > >>> > >>> > >>-- > >>Howard M. Lewis Ship > >>Independent J2EE / Open-Source Java Consultant > >>Creator, Jakarta Tapestry > >>Creator, Jakarta HiveMind > >> > >>Professional Tapestry training, mentoring, support > >>and project work. http://howardlewisship.com > >> > >>--------------------------------------------------------------------- > >>To unsubscribe, e-mail: > [EMAIL PROTECTED] > >>For additional commands, e-mail: > [EMAIL PROTECTED] > >> > >> > >> > >> > > > > > >-- > >The Spindle guy. http://spindle.sf.net > >Get help with Spindle: > >http://lists.sourceforge.net/mailman/listinfo/spindle-user > >Announcement Feed: > >http://www.jroller.com/rss/glongman?catname=/Announcements > >Feature Updates: > http://spindle.sf.net/updates > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: > [EMAIL PROTECTED] > >For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > Konstantin Ignatyev PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000 Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
