Any good reason for using Entity Beans?

[Jes�s Vi�uales Bueno]

Hello everybody.   First of all, sorry for my question.   Till now, I was using an Application Server which didn't support Entity Beans, and as my new Appiclation Server supports them, I must ask you that question.   Since I think that almost all the server work can be done using Stateless Session Beans (inserts, updates and so on into the database), is there a good reason to use Entity Beans for representing table rows?   Isn't there lots of overhead (creation, remote invokes and so on) if you only want to make an insert? or only an update?   Since the DB surely has it's own cache mechanisms, Entity Beans cannot be used in order to cache data in the server memory.   One last question: if my DB has load balancing mechanisms, I think that that performance improvement will be lost using Entity Beans.   Maybe this question has already been answered in this forum, but I'm really very interested in your oppinion.   Please sorry if you think I'm a fool but I can't understand the reasons for having Entity Beans.   Abstraction of SQL calls? Ok, use helper classes.     Thank you very much and sorry for my lack of faith.   Jesus