Article:		Enterprise Application Integration using Apache Cocoon 2.1
Subject:		Scalability, Maintainability
Date:		2003-11-19 02:05:08
From:		Tony Culshaw
Response to: Scalability, Maintainability
Glad you enjoyed the article, sorry I took so long to reply. A high end wintel with plenty of memory should handle up to 30ish trans/sec with Apache Web Server in front of the servlet engine. There's no doubt that XSLT and the pipeline model cost more in terms of processing power, but then the same can be said about java compared to C/C++, or C/C++ compared to assembler! Spend more on hardware and have an elegant solution rather than cost more in time and developer pain. Regarding your excessive use of xslt ... in theory you can do the whole thing in XSLT, but I would call that excessive. It is however interesting to see how far you can take it. Our main business logic and persistence engine is all J2EE/JBoss. The middle of the road approach is to use whatever framework gets the job done. If we all believed in pure OO development why aren't we all using Object Databases instead of our old clunky Relational Databases? My final comment regards 'try-and-error' development. I have to admit that all my development is in fact 'try-and-error'!

Previous Message

Up

Next Message