[nylug-talk] Why does "enterprise" imply "Java"?

[alex@pilosoft.com]

On Thu, 6 Jul 2006, Eric Moore wrote:

> "Felix Shnir" <felix.shnir at gmail.com> writes:
> 
> > Err, there is a reason why java is considered enterprise. J2EE contains a
> > lot of meat that neither PHP nor ruby with or without rails has.
> >
> > Give me an example of JNDI tree or architecure in either?  Or EJB
> > session / messaging?  or their respective server management across
> > clusters?  Granted there is a right tool for each job, but
> > "enterprise" in java is exactly the ability to do n-tier
> > architecture with unlimited scalability.
> 
> Could you perhaps rephrase this with a little less buzzword-compliance?  
> I mean, I know EJB is "enterprise java beans" but what does the
> session/messaging do?  I'm pretty sure the j in "JNDI tree" also stands
> for Java, but We should be able to discuss what the features DO without
> being java programmers.
You should be able to discuss things by googling, though.

I hate to take enterprise's side in this, but perhaps nylug isn't exactly 
a place that would even *know* what is necessary in the enterprise.

JNDI is java naming and directory interface - basically, you can register 
that your application provides service 'bar' and then request location of 
the service providing 'baz'. J2EE is all about providing *frameworks* that 
can be used to enhance scalability. 

> And as someone from the world of computational science, I assure you,
> not all problems have unlimited scalability, regardless of how wiz-bang
> your programming language and libraries are.  So what problems are you
> scaling in an unlimited fashion? :)
Put it this way: Of course, nothing has unlimited scalability.  
Nevertheless, J2EE provides a large portion of a framework that is
necessary to scale things.

--
Alex Pilosov    | DSL, Colocation, Hosting Services
President       | alex at pilosoft.com    877-PILOSOFT x601
Pilosoft, Inc.  | http://www.pilosoft.com