I'm looking for a
pattern that would enable me to have a class that calls different processing steps in a sequence where the result of each sequence will determine if the next sequence happens or not. Each of those sequences are coded as an implementation with a certain behavior which will be called by the orchestrator service. Currently, each of those service will throw an Exception which is handled by the orchestrator service. There may be multiple such orchestration services having different sequences. Is there any design pattern that I can look into?