You would not use the embedded process engine approach. Instead run a remote process engine and implement service tasks in Go using the external task patter. To get such a remote engine you can either just sign up for a free developer account on Camunda Cloud. If your prefer on premises, then you can use a self-managed deployment (e.g. via docker compose). For both options check here: https://camunda.com/get-started
发布评论
评论（1）
您不会使用嵌入式工艺引擎方法。而是运行远程流程引擎并使用外部任务模式在GO中实现服务任务。要获得如此遥远的引擎，您可以只注册Camunda Cloud上的免费开发人员帐户。如果您喜欢在房屋上，那么您可以使用自我管理的部署（例如，通过Docker组成）。对于这两个选项，请在此处查看： https://camunda.com/get-started
一旦您拥有引擎和配置的凭据（请关注 https://docs.camunda.io/docs/guides/guides/开始/）。
显示了如何在过程引擎端配置服务任务。如下所述，您现在可以实现外部工作（示例中的ZBCTL）： https://github.com/camunda/zeebe/tree/main/main/clients/go
You would not use the embedded process engine approach. Instead run a remote process engine and implement service tasks in Go using the external task patter. To get such a remote engine you can either just sign up for a free developer account on Camunda Cloud. If your prefer on premises, then you can use a self-managed deployment (e.g. via docker compose). For both options check here: https://camunda.com/get-started
Once you have an engine and configured credentials (follow https://docs.camunda.io/docs/guides/getting-started/).
The section https://docs.camunda.io/docs/guides/getting-started/implement-service-task/ shows how to configure the service task on the process engine side. On the Go side you can now implement an external worker (instead of zbctl in the example) as described here: https://github.com/camunda/zeebe/tree/main/clients/go