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

[Michael Bacarella]

On Thu, Jul 06, 2006 at 03:17:40PM -0400, Ajai Khattri wrote:
> Dan Crosta wrote:
> >I was under the impression that "Enterprise" referred to the ability to
> >scale to multiple machines, N-tier architectures, load balancing,
> >distributing processing
> 
> You can do the same thing with PHP or Ruby on Rails. This tells me that 
> either people dont know this or as usual its down to marketing BS.

When someone Google searches "Spring", you see:

	Spring and XFire for implementing Web Services
	Submitted by Colin Sampaleanu on Wed, 2006-05-31 09:30. Technical Article

	Tsolak Petrosian shows how to expose an EJB 2.1 Session Bean as a web service
	with Spring and XFire, in XFire+EJB+POJO+HTTPSECURITY. The EJB is hidden behind
	a dynamic proxy that XFire is wired to.

	Marc Logemann shows how to expose a simple web service using Annotations in Web
	Services with Spring, XFire and JSR 181. 

	Basic Spring Web Services with XFire and JSR 181 provides additional information
	on the subject. » login or register to post comments

Search "PHP" and you get:

	PHP  is a widely-used general-purpose scripting language that is especially suited for Web
	development and can be embedded into HTML. If you are new to PHP and want to get some idea
	of how it works, try the introductory tutorial. After that, check out the online manual,
	and the example archive sites and some of the other resources available in the links section.

You're onto something.

Maybe someone should tell the PHP guys that they'd go further if something like this appeared
in the Google results instead:

	PHP - The Missing Link in the Biotech Enterprise
	Submitted by $Swedish_First_Name on Fri, 2006-05-31 5:45AM.  Integration Article

	$Eastern_European_Name has produced a paper on applying PHP to Genomics analysis
	workflows by synchronizing from XMLRPC-over-SSL visualization Web Services.
	The image data is generated from multiple parallel secondary visualization N-tiered
	servers using GD frontends wired to Berkeley XML DB engines and cached on Squid
	proxy-content servers.