Hi All,
I would like to clear my doubts about the usage of
EJB in the J2EE application.
When to use EJB instead of
servlets + javabeans +
jdbc api? In my application which contains normal transactions (view/modify/delete, 10000 users + assumming max 100 users doing concurrent transaction), I have used the MVC architecture and deployed in weblogic app server and the application is currently running fine with out any problem.
What will happen if we replace the javabeans + jdbc api with EJB? Do the performance will improve? ( I have read that using Entity beans will affect the performance? Or making the servlet as a controller and put the business logic in the session bean just to differentiate control logic from bus logic.)
I read that EJB means for transactions, security, distributed computing and no need to be expert in SQL Language, But I think we will use the same transaction code in both cases as we are getting the connection from Connection pool(Assuming that I am not changing the transaction parameter in the deployment descriptor!!). Except the security and distributed computing do we need to use the EJB if the developer is well verse in SQL Coding?
In our application we are using our own security mechanism to authenticate & Authorize the users. I am using the servlets + javabeans for distributed computing. So why EJB?
Thanks & Regards,
M.S.Raman
