locked
SOA Architecture RRS feed

  • Question

  • User-1636183269 posted

    Hello,

    I am using SOA architecture, any one please guide me what major and minor thing we need to take in long running.

    Thanks in advance.


    Tuesday, March 2, 2010 2:41 AM

Answers

  • User-1659704165 posted

    Hi,

    SOA(service orinted Architecture) Webservice and WCF will Take care..



    OR


    http://www.15seconds.com/issue/031215.htm

    http://www.c-sharpcorner.com/UploadFile/john_charles/Service_Oriented_Architecture_and_Microsoft_NET01202006080616AM/Service_Oriented_Architecture_and_Microsoft_NET.aspx

    http://www.aspcode.net/Simple-ASPNET-SOA-architecture.aspx


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 2, 2010 3:21 AM
  • User-952121411 posted

    Here are some of the 'Pitfalls' of SOA you may want to be aware of going forward:

    Avoiding common pitfalls in SOA adoption:

    http://www.ibm.com/developerworks/library/ar-soapit/

    Top 8 SOA Adoption Pitfalls: 

    http://www.infoq.com/articles/Top-8-SOA-Adoption-Pitfalls

    Top 10 SOA Pitfalls:

    http://www.theserverside.com/news/thread.tss?thread_id=49938

    Avoid SOA Pitfalls!

    http://soa.sys-con.com/node/318417

     

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 2, 2010 9:44 AM
  • User78336405 posted

    Hi,

    SOA confers obvious business benefits associated with integration and the creation of new services. However, insufficient attention to governance—the management and monitoring of services, their performance and reliability, and especially their security—can cause inefficiencies and disrupt business processes and the end users they support. As business needs evolve, it is critical to have policies in place that help determine how to prioritize new business processes and services under consideration for implementation, who will be responsible for designing those processes, how they should be implemented, and how the success of the new implementations will be measured. This is especially important given the inherent cross-functional nature of SOA solutions.

    Reuse of services, once touted as a primary SOA advantage, is really a byproduct of the approach rather than the goal itself. Reuse is also proving to be more challenging than expected. An existing service may not provide exactly what a different business process requires and so may call for additional work. And designing a service so that it can be reused in the future requires accurately predicting what future needs will be, something notoriously difficult to do.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, March 4, 2010 12:15 AM

All replies

  • User-1659704165 posted

    Hi,

    SOA(service orinted Architecture) Webservice and WCF will Take care..



    OR


    http://www.15seconds.com/issue/031215.htm

    http://www.c-sharpcorner.com/UploadFile/john_charles/Service_Oriented_Architecture_and_Microsoft_NET01202006080616AM/Service_Oriented_Architecture_and_Microsoft_NET.aspx

    http://www.aspcode.net/Simple-ASPNET-SOA-architecture.aspx


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 2, 2010 3:21 AM
  • User-952121411 posted

    Here are some of the 'Pitfalls' of SOA you may want to be aware of going forward:

    Avoiding common pitfalls in SOA adoption:

    http://www.ibm.com/developerworks/library/ar-soapit/

    Top 8 SOA Adoption Pitfalls: 

    http://www.infoq.com/articles/Top-8-SOA-Adoption-Pitfalls

    Top 10 SOA Pitfalls:

    http://www.theserverside.com/news/thread.tss?thread_id=49938

    Avoid SOA Pitfalls!

    http://soa.sys-con.com/node/318417

     

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 2, 2010 9:44 AM
  • User78336405 posted

    Hi,

    SOA confers obvious business benefits associated with integration and the creation of new services. However, insufficient attention to governance—the management and monitoring of services, their performance and reliability, and especially their security—can cause inefficiencies and disrupt business processes and the end users they support. As business needs evolve, it is critical to have policies in place that help determine how to prioritize new business processes and services under consideration for implementation, who will be responsible for designing those processes, how they should be implemented, and how the success of the new implementations will be measured. This is especially important given the inherent cross-functional nature of SOA solutions.

    Reuse of services, once touted as a primary SOA advantage, is really a byproduct of the approach rather than the goal itself. Reuse is also proving to be more challenging than expected. An existing service may not provide exactly what a different business process requires and so may call for additional work. And designing a service so that it can be reused in the future requires accurately predicting what future needs will be, something notoriously difficult to do.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, March 4, 2010 12:15 AM