Hey
Alain Rogister wrote:
> Looks like our old friend Roger Sessions has written another comical
> masterpiece. A few out-of-context quotes to whet your appetite:
<snip>
*Sigh*... 'nuff said...
It is interesting that he begins the issue by pointing at a customer
case who has had problems deploying with EJB (which we don't really
*know*, but Roger wants it to look that way).
Well, during the past months we have had lots of headlines in Swedish
computer zines about MTS-based sites doing really really bad (see
Computer Sweden articles on boo.com and boxman.se for example).
Scalability issues delays in development was the most frequent reasons.
Everyone has problems, the questions is what the underlying issue is: is
it an inherent problem with the architecture or the specific product, or
use of it. It doesn't matter if every 3rd party tool is perfect if the
particular development team doing an application makes mistakes. And
that can happen to everyone, regardless of tool.
> "The result of all this was a poorly thought out Enterprise JavaBeans
> architecture that was unleashed on a naive industry."
Indeed, some of the more interesting features such as EntityBeans (I
have a pretty good feeling this is what he's most objective too)
requires a lot of maturiy and understanding on behalf of app developers
to work properly. The most frequent Q's here and on developer oriented
forums are related to the use, design and implementation of EntityBeans.
But these issues are more related to EntityBeans being a rather "new"
concept (as opposed to SessionBeans, and their rather
down-to-earth-esque use), than inherent problems with EB's. IMHO of
course.
> "So whereas Sun is frantically adding features to EJB, Microsoft is
> quietly removing them from COM+. In Memory Databases (IMDB) was one of
> the highly touted features of the COM+ Beta. Unfortunately IMDB had many
> of the same problems as EJB's Entity Beans, namely a poorly defined
> integration between the component level cache and a database level
> cache." [His name isn't Roger "Sessions" for no reason]
IMDB sucked as a concept, but its inherent design screwups are nowhere
near comparable to EntityBeans. The only thing in common is "state
caching". But from there on they are wildly different when it comes to
design and implementation.
> "Microsoft's attitude is to make sure that what is there works; if
> Microsoft isn't absolutely convinced that a particular feature makes
> sense, out it goes."
Which is what any reasonable software company would do. What's so novel
about it? Geeez...
/R
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
