[ajug-members] Popularity of Java skill sets for jobs

[Burr Sutter]

I do appreciate your point and think it is very valid.  EJB2 Entity beans
were an example of "lemmings" - everybody jumped off the cliff together.
Perhaps one good rule of thumb is understanding the pain level associated
with adopting a technology. Is it your learning curve pain? Or is a problem
with the technology itself? EJB2 SLSBs were fine as long as people
understood the value of the tool but using entity beans were only for the
techno-masochist.

Good point on iBatis vs Hibernate - but I think both are relatively popular
therefore are reasonable longer term bets.  I'd rather not be in the
business of rolling-my-own persistence framework again, nor my own MVC
architecture with a widget library.

Your point about SOA being hype driven architecture (HDA) is also valid (and
I'm one of those people pushing the SOA paradigm).  The otherside of the
hype coin is that most IT organizations don't tend to move until the hype
forces them to.  Many IT shops would have been happy without Java or even
web-based solutions but they also didn't wish to be left out of party.  The
challenge is related to a paradigm shift like mainframe to client/server and
client/server to web.  In this case, application silos to SOA. When to move?
Why move?

It is hard to guess when making a move is a "must-have" vs a
"nice-to-have".

All this is to say, for me, I'm a hype follower, I watch and try to learn
the "popular" options as I don't wish to be paradigm shifted out of the
development market.

On Tue, Jan 6, 2009 at 11:01 AM, Rick <rickcr at gmail.com> wrote:

> 2009/1/6 Burr Sutter <burrsutter at gmail.com>:
> >
> > Picking "popular" solutions normally allow for easier maintenance over
> the
> > long tail of application maintenance.  Here is a more concrete example,
> in
> > 2014, where will you find people knowledgeable in WebObjects if you
> choose
> > it instead of Struts?
>
>
> Although the flipside is true as well, look at all the people that
> used EJB2 stuff just because it's "J2EE." I'd say that added to much
> higher maintenance costs over time (same thing with many using
> Hibernate over something like iBATIS - not meant as flame bait or
> anything... I like both. Depends on the task at hand though.)
>
> As a side note all these huge SOA approaches in corporations I think
> is another "buzz word" concept. For some things it makes sense, but I
> see many companies looking to SOA solutions for problems that don't
> even exist.
>
> _______________________________________________
> ajug-members mailing list
> ajug-members at ajug.org
> http://www.ajug.org/mailman/listinfo/ajug-members
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ajug.org/pipermail/ajug-members/attachments/20090106/39efafd4/attachment.html