Service-Orientation and the Windows/.NET Developer (CTS200)

A non-standard :-) session, based on Q&A instead of slides ... It was a good idea Don, expecially in a session late in a long day.

The key concepts of this session, as I understood since my bad English understanding :-), were:

  • SOA: Set of ideas for structuring software
  • Protocols: not just ideas but concrete to move the bits on the wire
  • Web Services: a set of protocols
  • Protocols natively supported by Indigo (out of the box ... in the future...)
    • SOAP over HTTP (one-way and request/response)
    • SOAP over TCP
      • Not faster than HTTP
      • Duplex messaging
    • SOAP over IPC (locally for security reasons)
      • Faster than HTTP and TCP
      • Duplex messaging
    • SMTP: there's no time... if we won't Indigo before 2009 :-)
    • MSMQ: why not ... may be...
  • A kind of TCPChannel + BinaryFormatter will not be supported because in .NET Remoting, using tcp+binary, there're some issues:
    • Version brittleness: you pay the pains of versioning
    • Performance issues: it's good but not great, because of lack of testing and evolution during the time
    • Security-ness: there's no security built-in
  • In order to work with a "contract-first" approach in .NET 2.0 we can:
    • Use WSDL.EXE /SERVER as before
    • WhiteHorse designer
    • WSDL (XML) editor provided by VS2005 with intellisense (great!)
    • Third party tools :-)
  • OO is like microelettronics. Every microchip needs its socket, with the right number of pins. When we use Objects we're using something with which we're always 100% comfortable and build to do exactly what we're asking it to do. Object are difficult to version. There's no way to have real transparent versioning.
  • SO is for agile development and deployment, for field replacement and great versioning. Share schemas and contracts in order to achieve these goals. SO doesn't require to share DLLs on both the sides. So deployment and versioning are easier than with OO.
  • SO in Longhorn:
    • for instance WMI will be redone in SO
  • Business Agents: the next buzword (in TechEd 2006... stay tuned :-) !)

 

  • Many other questions will be answered on Don's blog.

No Comments