Adam Schwartz - FM wrote: > I have been doing research on Jini for the last week, as I am considering > using it as a means of communication between servers on the backend of a > large-scale database driven website. > > The JINI model I have come up with is roughly: > servlets <--JINI--> JavaSpace <--JINI--> Backend programs <--JINI?--> > Database > > It seems an Enterprise JavaBeans application server could do all of this > already and save me a lot of time. Of course it costs an arm and a leg but > my company can deal with that. > > My main concerns for the solution are : scalability (adding machines should > be simple and not limited), no single point of failure, efficiency, and > deployment time, and dependability. > > JINI seems to excel at scalability and cost. Deployment time would > obviously be longer than EJB. I'm not sure about single point of failure > since it seems very difficult to get the JavaSpace to not be a single fail > point. Efficiency is an absolute black area to me, I have no idea how > efficient JINI is for this application. Dependability is also an issue > since none of my code is tested yet (since it hasn't been written!). > > EJB is obviously costly. Depolyment is quick. It claims to be very > scalable, but my concern is that we would have to buy another $10,000 server > license every time we want to add power. Does having only one EJB server > create a single point of failure? It seems so, perhaps 2 EJB servers can > act together as one (the way JINI lookup servers can, but JavaSpaces seem to > be unable to do). I assume that efficiency is high, since this standard is > so widely adapted and so many resources have been put toward development. > Dependability is also high since all of this code is tested. > > I'm scared of the single point of failure issue, i very much want to > eliminate a fail point in my system. > > Any thoughts, advice? > Are there good articles about this out there? Why don't you just kept doing EJB? I find these comparisons between EJB and Jini very annoying. At this point alot of Jini developers don't care about this issue. They already know which one is better and why. If your now trapped and now realize that your company can't afford a "scalable" EJB architecture, who cares? If you recommended EJB without realizing this it's your own problem. Forgive me for being blunt :-) =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
