版权声明：本文为博主原创文章，未经博主允许不得转载。不经过允许copy,讲追究法律责任，欢迎加入我们的学习提升群523988350，可以相互交流 https://blog.csdn.net/qq_30739519/article/details/89434812
本为主要罗列一下zeebe工作流的开发路线以及长久路线。
Zeebe目前处于我们称之为“开发者预览”的状态。这意味着：
- Zeebe正在进行大量开发，核心组件可能仍然需要重构。
- Zeebe API不稳定
- 系统的初始范围尚未完全开发出来。
- Zeebe目前不打算用于生产
在这个路线图中，我们提供了一些关于我们目前正在进行的工作的洞察力。我们将在每个季度初更新此页面。
很重要的一点是，该路线图不具有约束力，而且这里列出的功能可能会无限期地延迟或搁置——不过，当发生这种情况时，我们会做一个记录。我们还将指出何时将特性添加到正式的Zeebe版本中。
季度路线图
Q2-2019
- 使Zeebe集群永久运行成为可能：要启用长期运行的集群，Zeebe将需要删除执行活动工作流实例不再需要的数据。
- 仅在运行时保留一定数量的快照；删除较旧的快照
- 删除早于最低快照/导出器位置的日志块
- 确保Zeebe集群具有容错性：为了使Zeebe做好生产准备，我们需要对其进行强化并广泛测试其容错特性。
- Zeebe群集可以完全重新启动
- 节点可以在运行时重新启动（例如，支持滚动升级）
- 群集可以从网络分区恢复
- 完全数据丢失后节点可以重新加入
- 为Zeebe的生产使用提供用户指南：为了确保用户能够自信地在生产中运行Zeebe，我们将改进文档并添加新条目。
- 为在Kubernetes上部署Zeebe创建部署指南（例如，使用Helm图表）
- 创建一个Zeebe“production readiness checklist”，以便用户准备在生产中管理Zeebe集群。
Q1-2019
- 支持BPMN:
- Message/Timer non-interrupting boundary event (Completed in Zeebe 0.15)
- Message/Timer start event (Completed in Zeebe 0.15)
- Payload concept to support scopes and concurrency: Use a scope-based variable store, which makes it possible to propagate payload changes in scope hierarchy. (Completed in Zeebe 0.16)
- Improve error messaging from user perspective: Improve visibility and details of user errors, which allow better understanding and handling of error cases. (Completed in Zeebe 0.15)
- Inital infrastructure changes to improve stability: Initiate required changes to improve the cluster stability in the upcoming releases, particularly around cluster membership, failure detection and replication. (Incomplete - To Be Continued in Q2-2019)
Q4-2018
- BPMN support:
- Intermediate timer event (Completed in Zeebe 0.13)
- Event-based gateway (Completed in Zeebe 0.14)
- Message/Timer interrupting boundary event (Completed in Zeebe 0.14)
- Message/Timer non-interrupting boundary event (Incomplete - To Be Continued in Q1-2019)
- Message/Timer start event (Incomplete - To Be Continued in Q1-2019)
- Payload concept to support scopes and concurrency: Use a scope-based variable store, which makes it possible to propagate payload changes in scope hierarchy. (Incomplete - To Be Continued in Q1-2019)
- Decouple incident resolution from state changes: Decouple incident resolution through state updates from continuation of workflow instance execution. (Completed in Zeebe 0.14)
- Improved error handling and reporting: Provide better error propagation for client and operations tools by introducing error types and supporting custom job worker error messages. (Job error message completed in Zeebe 0.14)
Q3-2018
- BPMN support:
- Embedded sub-process (Completed in Zeebe 0.12)
- Parallel Gateway (Completed in Zeebe 0.12)
- Intermediate Message Catch Event (Completed in Zeebe 0.12)
- Receive Task (Completed in Zeebe 0.12)
- Scalable state management based on RocksDB: State of active workflow instances is stored in RocksDB, a widely-used, embeddable, and fast key-value store that can spill to disk when necessary. (Completed in Zeebe 0.12)
- Message correlation with TTL support: Zeebe will correlate a message with one or more workflow instances based on a shared correlation key. The user can define a message time-to-live (TTL), and Zeebe will “buffer” a message and correlate during this TTL. (Completed in Zeebe 0.12)
- Exporter API to stream data out of Zeebe: Zeebe will manage data for the state of active workflow instances, and users can choose to stream historic workflow data into a storage system of their choice. Exporters make it possible to create an audit log of all workflow events for future analysis. (Completed in Zeebe 0.12)
- Switch to gRPC client protocol and gateway: This change makes it easier to both create and maintain Zeebe clients in any gRPC-supported programming language. The gateway will make it easier to deploy and secure a Zeebe cluster. (Completed in Zeebe 0.12)