Confused: WS, SOA, Messaging any better than CORBA?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jules (Roseanna80_at_hotmail.com)
Date: 09/26/04 

Date: 26 Sep 2004 11:48:26 -0700

Hello

I am still trying to grapple with Web Services, SOA, Messaging, so
please excuse my ignorance.

I can build and consume (Request/response) Web services with Visual
studio pretty easily. Visual Studio, makes these look like Internet
accessable remote procedure calls RPC. Sort of like CORBA being
allowed through http enabled Internet firewalls.
  
So now I try to understand SOA, and the emphasis it being a message
based paradigm. This is where I get confused, even WS Enhancements
appear to be generally based around request/response interactions. I
can see in the WSDL defitnion an opportunity to do a Request Message
only, or Response_Message only, but there seems to be little in the
WSE 2.0 to support this across http. So I appera to be limited to RPC
style interactions across http. I am reading Url SOA framework book,
and he is makes the distinction between RPC and Document based
payloads. So I am looking for some concrete examples of doing this in
WSE 2.0.

My real confusion is that I don't see 'messages', I can receive
documents to consume. But there are no message Queues, so it doesn't
look like any MOM based infrastructure I have seen before. I cannot
queue up messages if processor overloaded, or the server is down. So
why say that SOA its message orientated. Are we really going to get a
WS standard that gives us true message orientated services. I know I
can stuff MSMQ on the end of a web services, but this is true Internet
wide service. (The web servcie may not be there. But I guess there is
nowhere on the Inter Netwrok to queue the messages anyway)

My other confusion is that with WSE 2.0, to perform Request Only,
Notification only, interactions I can only do this on TCP based
channels (Because http only seems to support requests/response
interactions, which is a RPC pardigm.) So I seem to be constrained to
the RPC paradigm, for cross Internet interaction. If I am stuck with
TCP, I might as well continue with CORBA, since TCP ports will not get
through Internet Firewalls.

At least with CORBA I have a mix of RPC and true messaging.

Looking forward to the day that WS providing a Queued Messaging
standard.

Many Thanks for any clarifications or reference to clearer SOA links.

Jules

Relevant Pages

  • Re: Confused: WS, SOA, Messaging any better than CORBA?
    ... > I can build and consume Web services with Visual ... > allowed through http enabled Internet firewalls. ... > So now I try to understand SOA, and the emphasis it being a message ... So I appera to be limited to RPC ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Converting an application to support Web Services ...
    ... Maybe u missed smth, but the last version of SOA is not RPC at all, it's message orient, bases on the document style. ... A> web services. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Few questions on SOAP
    ... I was reading on SOA or Service Oriented Architecture for last few ... You are mixing it up with SOAP, which is a web services ...
    (comp.lang.python)
  • Re: Service Oriented Architecture Question
    ... been having heated debates about SOA for years now and there is still ... to design services and implement an SOA and the amount of information ... The first thing I'll stress is that "web services" do not equal ... on top of business components that access this data access layer. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Buzzwords that need to die...
    ... Why not use the normal term, Web Services. ... Well I guess SOA is somewhat ... Architects design Systems, by providing system blueprints (UML, ... Developers, Network Engineers, and Security ...
    (borland.public.delphi.non-technical)