0 Replies Latest reply on Sep 17, 2009 10:55 AM by kurt steele

    Strategies for packaging related services?

    kurt steele Newbie

      I am using the basic 3-layer classification of my ESB services, basic, composed and process.

      Right now I need to deploy 10 or so basic services implementing atomic file system operations.

      I'd like some feedback on packaging strategies. It would make sense to me to put all of my read/write/delete/copy/etc operations for one domain in one .esb archive.

      The O'Reilly SOA Cookbook was very much against this and gave versioning, redeployment and coupling as reasons to avoid it. I just don't want thousands of .esb files floating around, even with a solid naming scheme.

      Also, how can my physical deployment accurately capture my classification scheme?