viernes, 2 de octubre de 2009

Pipelines
more than an architectural style/pattern

Every morning when I wake up, I thank god for the new day, my health, the family and for the pipeline architectural style!!

Pipelines (PL) provide enormous flexibility, Loosely coupled systems, policy, security and logging reinforcement and lot more. Pipelines allow to process the "data-in-flow" in an orderly fashion, and by applying an strategy based on pure "Separation of Concerns".

Modules plugged into the PL, are highly cohesive and loosely coupled, so if one of them is removed, upgraded or changed, the others keep working transparently. This is a very convenient pattern when data processing needs to be performed "on the fly". Because of its flexibility and modularity, every component in the PL watches the "data-in-flow" for some specific patterns (pattern recognition PATREC), in order to process, transform, change, adapt just the corresponding part the component is aware of (see the picture below).


PLs also allow to dynamically extend and change, existent behaviors by just de-registering/registering modules. PLs best practices along with Service Oriented Architecture (SOA) and ESB platforms, offer a promising future for business models looking for a "LEGO-Like" support on new products, that will reduce drastically the T2M.

No hay comentarios:

Publicar un comentario