Best practise packaging ESB archives, No. of Services per .esb?

[kjcooler]

Hi,

I've worked through the tutorials and am interested to know on what the best practise for packaging up services into ESB archives is?

I'm working on a project that has gone through a prototyping phase and would like to know whether it is preffered to package a single service into a single *.esb archive or whether multiple services per esb archive is acceptable and what the impact of this might be ?

My concern is that if we keep adding to a single project and single ESB archive, it will become harder to maintain in the furture, meaning the whole archive will need to be deployed. Packaging multiple services into a single esb archive doesn't feel very service orientated and I was just wondering what other people do?

Thanks in advance.

[beve]

Hi Kristian,

we usually only package a single service per esb archive so that we can redploy a service without having other services redeployed at the same time.

Regards,

/Daniel

[kjcooler]

Thanks Daniel this is what I was expecting.