Title: Message
ECPerf, and also the benchmarks by the CTS(I think, I can't remember if that's the acronym).
 
Entity Beans are a slower(not much) than use-case-hardcoded JDBC. But they're within the same order of magnitude, thus, large systems using EBs will benefit from a swifter development timeframe and lessened maintenance costs.
 
If you want something really fast, Assembler and Native drivers are the way to go.
 
Juan Pablo Lorandi
Chief Software Architect
Code Foundry Ltd.

Barberstown, Straffan, Co. Kildare, Ireland.
Tel: +353-1-6012050  Fax: +353-1-6012051
Mobile: +353-86-2157900
www.codefoundry.com
 
Disclaimer:
 
Opinions expressed are entirely personal and bear no relevance to opinions held by my employer.
Code Foundry Ltd.'s opinion is that I should get back to work.
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Vin�cius de Faria Silva
Sent: Wednesday, October 09, 2002 6:13 PM
To: [EMAIL PROTECTED]
Subject: the truth about entity beans

I've been following discussions about the pos and cons of entity beans for 2 years.
I'm not sure yet if this approach is good or not, mainly in terms of performance.
I hear a lot of system architects say that entity beans are slow.
What's the true about this issue?
Entity Beans are slow?
If not, which great J2EE systems(in production) are based on entity beans?
Are there benchmarks which proof that entity beans can provide good performance?
 
regards,
 
Vin�cius

Reply via email to