locked
SOA + .net RRS feed

  • Question

  •  

    Dear friends

     

    Can any body tell me

     

    1- What facilities microsoft provides for following SOA?

     

    2- What are problems with microsoft .net for SOA?

     

    3- Does Microsoft .net is use full for Enterprise Archetects?

     

    Thanks

     

    Regards

    Wednesday, August 8, 2007 8:23 AM

Answers

  • Hi Iqbal,

     

       may you take a look at the MSDN SOA page?

     

       In brief words, from the .NET (programming) side, MS offers at least three technologies very useful for coding SOA services and their clients:

     

    -Windows Communications Foundation (WCF) for addressing, binding and contracting services

    -Windows Workflow Foundation (Windows WF) for process orchestration

    -Windows Cardspace for Identity and Access in federated environments

     

       Those techs are cool for developers but still leave something to be desired in terms of monitoring (it's up to you adding some logic to monitor their behavior, elapsed times, etc). As an alternative, MS offers Biztalk Server which get easier the design and definition of orchestrated business processes (involving heterogeneous environments) in different formats, even opened ones like BPEL. Biztalk comes with tools for SLA definition and monitoring, being able to fire alarms when the thresholds are surpassed

     

       Lastly, MS announced guidance for ESB deployment on Biztalk Server. Those are available here: http://www.codeplex.com/esb

    Tuesday, August 14, 2007 9:22 PM
  • Hey Iqbal,

    You should also check the Guidance Automation Toolkit  and Software Factories, specially the web client software factory to begin with.

    Please tell me if you need any more resources.

    Tuesday, August 14, 2007 11:34 PM

All replies

  • Hi Iqbal,

     

       may you take a look at the MSDN SOA page?

     

       In brief words, from the .NET (programming) side, MS offers at least three technologies very useful for coding SOA services and their clients:

     

    -Windows Communications Foundation (WCF) for addressing, binding and contracting services

    -Windows Workflow Foundation (Windows WF) for process orchestration

    -Windows Cardspace for Identity and Access in federated environments

     

       Those techs are cool for developers but still leave something to be desired in terms of monitoring (it's up to you adding some logic to monitor their behavior, elapsed times, etc). As an alternative, MS offers Biztalk Server which get easier the design and definition of orchestrated business processes (involving heterogeneous environments) in different formats, even opened ones like BPEL. Biztalk comes with tools for SLA definition and monitoring, being able to fire alarms when the thresholds are surpassed

     

       Lastly, MS announced guidance for ESB deployment on Biztalk Server. Those are available here: http://www.codeplex.com/esb

    Tuesday, August 14, 2007 9:22 PM
  • Hey Iqbal,

    You should also check the Guidance Automation Toolkit  and Software Factories, specially the web client software factory to begin with.

    Please tell me if you need any more resources.

    Tuesday, August 14, 2007 11:34 PM
  • Regarding your q2.
    SOA is an architectural Style - .NET is a technology platform
    There is nothing inherent in .NET that prevents you from doing SOA. There are few technologies that are "SOA friendly" (e.g. WCF) - At the end of the day it is up to you Smile

    Arnon
    Wednesday, August 15, 2007 11:15 AM