That evil pipeline component constructor

Editorial architecture visual showing system boundaries, service interaction, and technical tradeoffs

So it took me almost three hours to find out why my pipeline component does not work correctly in the design time. It turns out its constructor has problem while initialize the enterprise library due to the ESB 2.1 installation. The problem is easy to fix but hard to discover, just a note.

Next step

Need this reviewed in a real system?

Use the article as a starting point, then bring the actual decision, constraints, and failure paths into an architecture review.

Join the discussion

Sign in to comment. Signed-in comments appear immediately.

Join the discussion