Wednesday, October 16, 2013

Demandware Graphical Pipelines Disadvantages

Hi,

Below are some disadvantages i discovered while working on demandware :

The graphical pipelines have a number of disadvantages. First, they are highly static and difficult to maintain. Above all, however, it is also theoretically impossible to work on a pipeline with multiple developers. The reason for this is that even the repositioning of a single pipe let leads to changes at various places in the XML file – a file in which the pipeline is ultimately saved. This leads to a situation where conflicts that occur when merging before checking-in to a shared repository are very difficult – or impossible – to resolve. In addition, the URLs that result from the pipeline model are strictly predefined (
...demandware.../PIPELINENAME-ACTION
)

Above all, i found implementing MVC model much better and easy in comparision to Graphical Pipeline.

Comments are welcomed.

Cheers,

Ujjwal Soni

1 comment:

Vipin said...

Total agree with u...
No point in comparing a file with latest repository while committing changes, because even a small change in pipeline, leads to changes at so many places in XML file

Nearly impossible to resolve conflicts in xml