1 Reply Latest reply on Feb 9, 2015 2:54 AM by Jorge Morales

    Bundling services for deployment

    Earnest Dyke Novice

      Greetings all,


      Our current strategy is to bundle all "related" services (i.e. all services related to Customer) into a single .war/.jar deployment. This of course creates contention within our services development teams when more than one team is working on services. My question to the community is: to what granularity do you deploy your services? Create a deployment for each service seems to me to be too granular but I am interested in hearing from others.


      Thanks in advance for any and all relevant responses.



        • 1. Re: Bundling services for deployment
          Jorge Morales Master


          I would rather use .ear for packaging, as:

          • Allows to bundle different SwitchYard composite applications into a single EE application, so developers can work on their specific SwitchYard app in parallel.
          • Still there is a single deployment unit for you consumer services, so updating is an all or nothing operation.


          At the end, the answer is dependent upon your needs, and the application architecture, so depends a lot on development granularity (as you mentioned), but also in operations (will my services be constantly updated, and if so, do I want a redeployment to affect other services?) Also the binding types play a factor here, as you normally want to deploy some services together depending on the responsibility, on the bindings between services, ...

          So there is no single answer here, there is whatever fits better your needs.


          My 2 cents.