This post originated from an RSS feed registered with Java Buzz
by Carlos Villela.
Original Post: So, do you need remote objects?
Feed Title: That's sooo '82!
Feed URL: http://www.jroller.com/rss/cv?catname=Technical
Feed Description: Carlos Villela's weblog. Everyday life, everyday software development, everyday musings.
I don't WANT remote object lookup. If I start thinking about accessing remote objects, I've already failed :-)
This strikes me. It goes totally against the "distributed computing"
trend we've seen on the latest years, which basically boils down to a
lot of incompetent people using EJBs either because they're standard or
because they think that, some day in the future, their application will
need to scale to a humungous number of concurrent transactions and
they'll need to scale to something like a Google supercluster. Did I
mentioned they usually do uninteresting intranet applications? Oh, no,
I didn't. Yeah, I've heard this kinda talk when designing an intranet
app - and it was no marketing dweeb talking to me - it was a senior
developer/architect, with a straight face, looking at me suspiciously
like if I was asking him to go back to the Clipper/xBase era.
Really, how many systems do you see everyday that need remote objects? Systems that need
to scale to the multi-gigabyte database, to the hundreds of concurrent
users? How much simplicity are you throwing away just because your
crystal ball told you that you'll need to scale? I'm not talking about
sacrificing manageability or mantainability here, as they are, indeed,
important to most systems that's going to be put into production out
there, because you actually need them from day one. I'm talking about
choosing the extreme scalability path 'just because'. 'Just because' is
definitely no excuse for anything on software development, unless
you're doing an experiment, trying new things out, looking for a cool
solution to a problem or something along these lines.
I'm sick and tired of all those 'Enterprise Architects' I had to and,
unfortunately, still have to work with. They're all so full of
themselves, so close-minded about design patterns and using only
standardized technologies ("Ooooh, Hibernate? No way we're using that -
it's useful, does what we want, but so does Entity Beans, then why
not?" is rather common around here these days). I'm sorry if you had to
go through all this rant if you are developing interesting applications
that really need EJBs, but please bear with me here - you're one of a
select few members of the "I need EJBs and I can prove it" group.
Previous Topic
