How much slower is EJB then than RMI? We use RMI fairly regularly and it seems relatively fast. I would have thought most of the beans put into an EJB server are basically just RMI-like RPC calls.
By relatively fast, I don't mean optimized to the milisecond, but OK for normal user perception. At 11:01 AM 2/22/2002, Rob Nagler wrote: >Perrin Harkins writes: > > Probably not a popular sentiment on this list, but if I read one more > > whitepaper about how someone's N-tier distributed-cache No-SQL-required > > point-and-click "solution" has great scalability even though it takes 5 > > seconds to display a simple page, I'm gonna hurl. > >Wow! 5 seconds that's fast. On the one EJB project I was on, it took >two minutes to render a page on a local 100mbps ethernet using a >single Java GUI talking to a single EJB server with nothing else on >the net. It was easy to fix. I created a single session bean which >let the client talk directly to Oracle. The performance improved by >100x. Naturally, the architect had a fit, because this broke the >clean separation between the client, the middle tier, and the >database. > >My favorite white papers combine EJB, CORBA, XML, HTTP, JSP, and COM >without actually explaining what the problem is. With these >technologies, there are certainly enough solutions. > >Rob __________________________________________________ Gunther Birznieks ([EMAIL PROTECTED]) eXtropia - The Open Web Technology Company http://www.eXtropia.com/
