Here's my thoughts and I ask for related feedback from the experts -- bascially everyone else
![Smile :-)](./images/smilies/icon_smile.gif)
Container-based Design Model - Pros:
1) It seems that a model where tasks are put into containers within the same job is easier to maintain, manage, and administer. 2) It also seems that the overall processing time is less.
Container-based Design Model - Cons:
1) Development seems more difficult as you can't just run a particular task in the container; you have to run the whole job. For example, if you are working on a series to export - transform - import, you can't just run the import task to test it; you have to run the entire job. 2) Using Before/After routines you have some control over the processing and can send messages etc. but it is not as convenient as just dropping a stage into the sequence.
Sequence-based Design Model - Pros:
1) There is more control over processing -- you can easily add a notification task to send a message or whatever after a job completes. 2) Development seems easier because you can work on each task individually (e.g., export, transform, import, etc.) without having to run the entire series to test it.
Sequence-based Design Model - Cons:
1) The overall processing time seems to be greater. 2) It can get a bit tedious if you are passing a number of parameters to lower sequences and jobs as you have to set up the parameters values for each job/sequence.