I think using a workflow orchestrator platform would be a great way to implement this use case.
You probably don't need that since all your functions are available in the same service, but using an orchestration platform will offer a lot flexibility as your service grows in complexity or when the need for orchestrating your use case across multiple services comes up.
An option for workflow orchestration is Netflix Conductor. Here is an article that talks about how to use Conductor to manage sequential tasks. Conductor platform has features to run flows in a distributed fashion as well, such as fork join, decisions etc. and this can be done across different services.
Ex: Service 1 hosting Function A, Service 2 hosting Function B and C. And you can build a flow running A -> B -> C while passing/referring to outputs from the previously executed functions without having to build any state management systems.
The above article was written as a response to this Stackoverflow question which is very similar to yours.
For clarity - I used to work at Netflix on the team that built and open sourced Conductor.
发布评论
评论（1）
我认为使用WorkFlow编排平台将是实施此用例的好方法。
您可能不需要这一点，因为您的所有功能都可以在同一服务中可用，但是随着服务的增长或需要在多个服务中启动您的用例时，使用编排平台将提供很大的灵活性。
Netflix导体是工作流编排的选项。这是一个文章 谈论如何使用导体来管理顺序任务。导体平台的功能也可以以分布式的方式运行流，例如叉子加入，决策等。这可以在不同的服务中完成。
例如：服务1托管函数A，服务2托管功能B和C。您可以构建运行A - ＆GT的流量。 b - ＆gt; c在传递/指的是先前执行的功能的输出时，而无需构建任何状态管理系统。
以上文章是作为对此 Stackoverflow问题的回应。与你的非常相似。
为了清楚起见 - 我曾经在Netflix在建造和开源指挥家的团队中工作。
I think using a workflow orchestrator platform would be a great way to implement this use case.
You probably don't need that since all your functions are available in the same service, but using an orchestration platform will offer a lot flexibility as your service grows in complexity or when the need for orchestrating your use case across multiple services comes up.
An option for workflow orchestration is Netflix Conductor. Here is an article that talks about how to use Conductor to manage sequential tasks. Conductor platform has features to run flows in a distributed fashion as well, such as fork join, decisions etc. and this can be done across different services.
Ex: Service 1 hosting Function A, Service 2 hosting Function B and C. And you can build a flow running A -> B -> C while passing/referring to outputs from the previously executed functions without having to build any state management systems.
The above article was written as a response to this Stackoverflow question which is very similar to yours.
For clarity - I used to work at Netflix on the team that built and open sourced Conductor.