Hey all,
I'm involved in a large project to port an existing app that's
currently running on mainframes/Cobal to a J2EE webapp.
I of course want to sell Turbine for use on the frontend (EJBs are on the
backend).
This project is in the initial stages and has had some consulting
done by a large bluechip company (can you guess who?). Since I'm the new
guy on the project, I want to tread lightly and have all the answers before
I try to shove a change to the front-end framework.
As I've said this project is *HUGE* ( for example over 1900 views and heavy DB
interaction ) and needs to scale. I've used Turbine successfully on many
mid-sized projects but am curious if it'll have any problems scaling to an app
this size. My main concern initially is with the singletons (screens and
actions loader). But I feel the shouldn't be a problem with load-balancing and
replication among application servers ( BTW they're using WebSphere...ugh ).
Does anyone have any experience/thoughts/forseeable problems with Turbine
scaling to an app this size?
Initially it'd be with JSP as the views (Velocity will be the next
selling point...baby steps ).
If I can sell this, it could be a another big step forward for Turbine in terms
of commercial use.
Any thoughts appreciated!
--
Dave Bryson
[EMAIL PROTECTED]
----------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
