I am now using Turbine for all 3-tier projects that are being
developed in the company I work for. The framework is excellent, and
the programming model really shines in terms of separation of
presentation, logic and data. The apps we are building include
accessing transaction servers (via messaging protocols) as well as
RDBMSs (via JDBC).
There is a recurrent question that our clients raise every once in a
while, mainly due to a buzz-word problem: shouldn't we be using EJBs
to do all the encapsulation, and write all the reusable business logic
within EJBs to ensure it is reusable? After all these months of
acquiring experience with Turbine, I have a definite feeling that EJBs
are not really required for 90% of the cases, and that a well
structured servlet (Turbine), plus all kinds of services (Turbine),
plus what we call "connectors" to data back-ends, fit the bill nicely.
One point where I do see a place for EJBs would be if you had to
coordinate a transaction across multiple data back-ends; in this
case, two-phase commit would be invaluable. Since this case doesn't
really come up that often, the current reality is that we just have
not used EJBs at all, ever.
I would really love to hear other opinions on this matter, especially
from people with more experience than me (that would be easy to find)
in the EJB area. Have you used EJBs? Have you used them in
conjunction with Turbine? For what purposes? Does anybody think that
EVERYTHING should be encapsulated as an EJB?
Thanks for any input,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
