Clever Geek Handbook

Orchestration design template

I have three java components - ComponentA,

ComponentB,

ComponentC

. I want to organize this component. There can be several combinations (but sequentially) when performing these components, for example. ComponentA,

→ ComponentB,

→ ComponentC

or ComponentA,

→ ComponentC

. What's the best pattern here? Each component has its own functionality and is independent of each other. I am looking at the Java mediator pattern but not sure if it fits well in this case.

+3


source to share


3 answers


Perhaps the Chain of Responsibility pattern could fit this scenario.



+1


source


If you are dealing with complex entities in your Components and specific Data_flow, you can try to implement the Pipeline_software logical model . This will give you great control over your process. To be more specific, I can recommend Pipes and filters for you (although with MSDN you can still use its design).



  • Greetings
+1


source


I would recommend below

orchestra-tor -> component1 -> returns to orchestra-tor
orchestra-tor -> component2 -> returns to orchestra-tor
orchestra-tor -> component3 -> returns to orchestra-tor

This way you can loop through the component or inject business logic through the components later

+1


source






More articles:


All Articles