News: Amazon moves into web services using Java/C++

  • Thread starter Thread starter asj
  • Start date Start date
A

asj

BIG news from the web services front. Amazon will use web services to
tie all its vendors together. The company implementing the system will
be using Java/C++ (migrating to all-java later).

Isn't it funny how Microsoft spent so much touting .NET for web
services, and J2EE is actually taking a bigger slice of the pie?

http://www.internetnews.com/ec-news/article.php/3077221
 
: Isn't it funny how Microsoft spent so much touting .NET for web
: services, and J2EE is actually taking a bigger slice of the pie?

Web services were IBM's baby before Microsoft got involved.
 
Actually it is very funny.

MS had to make their way into an market where java had 7 years start. As we
all know, on the desktop people have used the best product for years, but on
conservative markets like servers, SUN and others had convinced people that
they NEED a big expensive server to compensate for the lack of performance
in enviromnents like Java. Proving them wrong could take a long time and be
very hard since when you get yourself into the hands of SUN you expect to be
robbed. As a step on the way, until people get to fully understand their own
good, MS made it possible for the rest of the world to make some use of the
old and expensive tech in Java by forcing SUN to abandon their non standard
way of doing things. Now people can see that exaktly the same thing in .NET
is 3 times as fast, 10 times easier to build but has a significantly lower
price.
 
: Isn't it funny how Microsoft spent so much touting .NET for web
: services, and J2EE is actually taking a bigger slice of the pie?

Web services were IBM's baby before Microsoft got involved.

That turns out not to be the case.

Briefly, the XML specification became a W3C recommendation in February
1998, and very shortly after Dave Winer published his interesting
comment that the next big thing would be RPC using XML over HTTP. In
mid-1998 Winer and Don Box were talking to Microsoft about what became
SOAP, and Microsoft even attempted to offer an early version to IETF
(which pretty much ignored it).

IBM got involved at the beginning of 2000, only a few months before
Microsoft announced the .NET strategy and SOAP was submitted to W3C.

Microsoft was emphatically the first major player to become involved
with Web services (in the now accepted sense of RPC- or document-style
communication over SOAP or XML-RPC).
 
Now people can see that exaktly the same thing in .NET
is 3 times as fast,

How could .NET, which is designed according to an architecture almost
exactly like J2EE/Java, be able to crank out 3 times better performance? Of
course, this does not take into account the "secret protocolls", design that
performs fast but does not scale, unfair tweaks and other stuff that mostly
goes into a benchmark comparison.
10 times easier to build

You seem to be on crack.
but has a significantly lower price.

Lower than what? Lower than JBOSS ($0.0)?
Lower than many inexpensive but good J2EE implementations?

Ixtlan
 
Tom Welsh said:
Briefly, the XML specification became a W3C recommendation in February
1998, and very shortly after Dave Winer published his interesting
comment that the next big thing would be RPC using XML over HTTP. In
mid-1998 Winer and Don Box were talking to Microsoft about what became
SOAP, and Microsoft even attempted to offer an early version to IETF
(which pretty much ignored it).

XML-RPC, which only sends the request and response data is much more
useful for "normal" calls anyway, without SOAP's excessive baggage
which is mostly there to make it harder to write implementations.
 
Ixtlan said:
How could .NET, which is designed according to an architecture almost
exactly like J2EE/Java, be able to crank out 3 times better
performance?
Of course, this does not take into account the "secret
protocolls", design that performs fast but does not scale, unfair
tweaks and other stuff that mostly goes into a benchmark comparison.

That pesky HTTP protocol, it's M$'s proprietary secret weapon! Plus the
other magical secret protocols we arent allowed to talk about <scary woo
noise>. No wonder those fiends get better performance!*

Christ, is "this group" (comp.lang.java.advocacy) turning into another
c.o.l.a. mouth frother's paradise or something?!

*of course, this better performance myth - you shouldnt have given it weight
by accepting it - it's M$ FUD or whatever.
 
Ixtlan said:
How could .NET, which is designed according to an architecture almost
exactly like J2EE/Java, be able to crank out 3 times better performance? Of
course, this does not take into account the "secret protocolls", design that
performs fast but does not scale, unfair tweaks and other stuff that mostly
goes into a benchmark comparison.

HEHE

The usual rant from poor losers when they can't grasp reality. Even SUN are
implementing the "secret" protocolls found in .NET and at last they are
improving on Java to support the featuers found in modern languages like C#.
It is realy fun to see SUN go from 7 years ahead to trying to "catch up".
You seem to be on crack.

I leave the drugs to the people of the OpenSource community. After all, they
have used it from start and that might explain things like GPL.
Lower than what? Lower than JBOSS ($0.0)?
Lower than many inexpensive but good J2EE implementations?

Ohh, so JBOSS has finally got a licence from SUN for J2EE??? Someone should
tell IBM so that they could trick their customers into another "it is free"
trap, forgetting to tell about their expensive support. In fact, if anyone
want to make money on OpenSource, they have to make sure that the product is
so hard to use that the customer is constantly forced to buy support. If
they ever actually manage to make it good, their income will go away.
 
begin said:

Grief, just look at the mangled quoting.
The usual rant from poor losers when they can't grasp reality. Even SUN are
implementing the "secret" protocolls found in .NET

Can't be secret if Sun are implementing them now can they? Do you
wintrolls ever read what you have written before clicking the send
button? No need to read any further.
 
Back
Top