Share via

Service Architecture Concept Model

  • Article

I'm posting this because I'm interested in your thoughts about it.

A Service Architecture Concept Model

IMPORTANT: This is just a concept illustration. I'm not encouraging anyone to accept and begin using the nomenclature used.

This is just the result of a conversation Tom and Ed and I had today about how this illustration might evolve. If something isn't clear, please leave a comment. If you've seen other illustrations or nomenclature about these things that better resonate with you, please leave a comment and tell me about them. If you have any other thoughts, ... I think you get the idea :)

https://dev4net.members.winisp.net/images/conceptmodel.png

Comments

  • Anonymous
    July 21, 2006
    In the original drawing, the business layer includes an element on top of Business Logic (BL) and Business Entities (BE), it's named Service Interface but guess that here could be named Business Interface. What should be there? The means of interacting with the BL & BE. I see the elements of the Service Interface Layer interacting with the Business Layer via the Business Interface and not directly calling the BE's and executing BL.
  • Anonymous
    July 21, 2006
    The comment has been removed
  • Anonymous
    July 25, 2006
    IBM has a similar chart "The layers of a SOA" (http://www-128.ibm.com/developerworks/webservices/library/ws-soa-design1/). You may be interested on taking a look. Both charts are
    awesome.
  • Anonymous
    August 02, 2006
    The comment has been removed
  • Anonymous
    August 02, 2006
    No, it's not a typo. One of the things we're trying to do is provide a name to each layer: Service Interface Layer, Business Layer, and Resource Access Layer (new term).

    The one thing I did fail to do in this graphic is include the Business Workflows (that was an accident). I'll fix it later and these comments won't make any sense :)

    In the Business Layer, the Business Entities,  Business Logic, and Business Workflows should be separate since because of their (loose) level of coupling to each other.

    Of course, if you're looking for typos, just hang around for a while ... it won't take long ;)
  • Anonymous
    August 03, 2006
    The comment has been removed
  • Anonymous
    October 20, 2006
    The comment has been removed
  • Anonymous
    May 02, 2007
    The comment has been removed
  • Anonymous
    December 13, 2007
    Many times the services are just part of a service layer interface or facade that only delegate calls