Welcome to MSDN Blogs Sign in | Join | Help

      Loosely Coupled Thinking

      SOA, BPM, Clouds &
      other trendy stuff...

News

  • Better Search:

    Tweets


      Reading

      About

      Not me but an incredibly realistic simulation.
      John Evdemon
      is an Architect
      at Microsoft.

      <legal-stuff>
      The views and opinions stated in this blog are mine and do not necessarily reflect those of Microsoft.
      Each posting on this blog is provided "AS IS" with no warranties, and confers no rights.
      </legal-stuff>

      Social

      View John Evdemon's profile on LinkedIn

      John Evdemon's Facebook profile





      Locations of visitors to this page

    Nailing Jello to the Wall

     

    Joe McKendrick has a blog entry about just a bunch of Web Services and SOA.   He cites some research from Saugatuck that states "...many companies are merely managing a collection of Web services, and have yet to make a strong commitment to SOA as a management discipline".  

    Joe asks: what constitutes a "proper" SOA? 

    I think the answer is simple – if it meets the needs of the organization its proper, if it doesn’t its improper.    

    One organization’s SOA may look like just a bunch of web services to another because they will have different business needs and objectives.

    (BTW - I refuse to grant the phrase "just a bunch of web services" acronym status.   You should too.)

    Posted: Wednesday, January 10, 2007 10:05 AM by jevdemon

    Comments

    J E E said:

    That bunch of web services would be part of a SOA if they 1) map 1-1 to the business services supported within the organization and 2) if they are managed (directory, mediation, virtualization) to meet the requirements of agility and reusability of the EA.

    It's even better if the services are used from an higher level, a BPMS or IC-BPMS (service orchestration, process management, activity monitoring).

    These two technologies (SOA and BPM) complement each other pretty well and should definitely play a much more important role in enterprise architecture.

    # January 11, 2007 12:26 PM

    jevdemon said:

    +1 on the convergence of SOA and BPM.  I'm not very happy with the IC-BPMS acronym - this is nothing more than categorizing products that already exist (causing more confusion into the SOA space - the last thing we really need right now).  

    # January 12, 2007 3:14 PM

    J E E said:

    Names will come and go ... Integration Broker, ESB, BPMS, IC-BPMS etc. IMO that is just a result of the prevailing unification between the technologies leading to the understanding of SOA/BPM.

    Btw: good job with the BPEL spec ... I'm a big fan that "language".

    # January 12, 2007 5:13 PM

    Loosely Coupled Thinking said:

    Sometimes thinking differently is a good thing. I'm not sure if this is one of those times . To be honest

    # January 22, 2007 3:00 PM
    New Comments to this post are disabled
    Page view tracker