We’re excited to announce Restate v1.4, a significant update for developers and operators building and supporting resilient applications. The new release improves cluster resiliency and workload balancing, and also adds a multitude of efficiency and ergonomics improvements across the board. Experience less unavailability and achieve more with fewer resources.
我们很高兴地宣布RESTUSE V1.4，这是开发人员和运营商建造和支持弹性应用程序的重大更新。新版本提高了集群的弹性和工作负载平衡，并且还增加了众多效率和人体工程学的改进。在资源较少的情况下，体验较少的不可用，并实现更多。
Lightning-fast node communications and network failure detection #
闪电快速节点通信和网络故障检测＃
Restate v1.4 enhances multi-node clusters with a new network fabric and gossip-based failure detection. This means lower overheads, more predictable latencies, and much improved reconfiguration and recovery during partial failures like network partitions.
RESTATE V1.4使用新的网络结构和基于八卦的故障检测来增强多节点簇。这意味着较低的开销，更可预测的潜伏期以及在网络分区（例如网络分区）期间的重新配置和恢复。
A significant improvement in v1.4 is the new gossip-based failure detection system. One of the hardest problems to crack in distributed systems is to reliably and correctly decide whether a given node is healthy, or if it is just temporarily unreachable from another node’s point of view. The new detection mechanism and partition placement deliver up to 10x faster detection of network partitions or node failures. Gossip is also used to disseminate partition leadership and other metadata updates for faster reaction to cluster reconfigurations.
V1.4的显着改善是新的基于八卦的失败检测系统。分布式系统中最困难的问题之一是可靠，正确地决定给定节点是否健康，或者从另一个节点的角度来看，它是否只是暂时无法到达的。新的检测机制和分区放置可提供更快的网络分区检测速度或节点故障。八卦还用于传播分区领导和其他元数据更新，以更快地对聚类重新配置的反应。
Restate using gossip to quickly disseminate liveness and leadership information for faster failure detection and reconfigurations.
使用八卦来重述以快速传播无能和领导力信息，以更快地检测和重新配置。
The faster failure detection and reconfiguration is visible in our Jepsen tests where we measure request latencies while inducing network partitions. The test runs a 3 node cluster and randomly partitions a single node from the rest before connectivity is reestablished. With Restate v1.4, the request latency was significantly lower, compared to Restate v1.3, showing the effectiveness of detecting node failures and reconfiguring the cluster to remain available.
在我们的JEPSEN测试中可以看到更快的故障检测和重新配置，在该测试中，我们在诱导网络分区的同时测量请求潜伏期。该测试运行一个3个节点群集，并在重新建立连接之前从其余的单个节点进行随机分区。与RESTATE v1.4相比，与RESTATE V1.3相比，请求延迟显着降低，显示了检测节点故障并重新配置群集以保持可用的有效性。
Measuring request latencies while our Jepsen test induces random network partitions in a Restate cluster (left: v1.3, right: v1.4). During the grey segments, a single node is partitioned from the rest. Note the logarithmic scale is used for the vertical (latency) axis. During the last nemesis phase between 60 and 70s, no requests are sent by the test.
在我们的JEPSEN测试中测量请求潜伏期，在重点群集中诱导随机网络分区（左：V1.3，右：V1.4）。在灰色段期间，其余的节点分区。注意对数刻度用于垂直（延迟）轴。在60至70年代之间的最后一个克星阶段，测试未发送任何请求。
The new messaging fabric creates separate network connections for different classes of inter-cluster traffic. This ensures that high-volume data intensive traffic doesn’t delay latency-sensitive traffic, maintaining predictable quality-of-service across the board. We also replaced GZip with Zstd, a more CPU-efficient compression algorithm, to reduce the size of messages that benefit from it. All of this means your applications will experience more consistent performance during normal operation and recover faster when nodes fail or network issues occur, improving overall system responsiveness and availability.
新的消息传递面料为不同类别的集群间流量创建了单独的网络连接。这样可以确保大量数据密集型流量不会延迟潜伏期敏感的流量，从而全面保持可预测的服务质量。我们还用ZSTD（一种更高的CPU有效压缩算法）替换了GZIP，以减少受益于此的消息的大小。所有这些意味着您的应用程序在正常操作期间将经历更一致的性能，并在节点失败或网络问题发生时更快地恢复，从而提高了整体系统响应能力和可用性。
Automatic partition rebalancing and orderly workload hand-overs #
自动分区重新平衡和有序的工作负载＃
Restate clusters will automatically perform partition rebalancing across configured nodes. This means better space and compute utilization across the board. Previously, partition scheduling made decisions based on the best available information at the time a decision was needed. However, over time, as nodes leave and re-join the cluster, this could result in uneven partition spread across cluster members. With v1.4, the cluster will actively rebalance the load and revisit previous placement decisions that are no longer optimal. Another improvement is that partition processors now go through explicit drain and warm-up phases, which further minimises the disruption during a leadership change – this in turn means shorter pauses and more predictable tail latencies for your applications.
重点群集将自动在配置的节点上进行分区重新平衡。这意味着更好的空间和计算利用率。以前，分区调度根据需要决定时根据最佳可用信息做出决策。但是，随着时间的流逝，随着节点离开并重新加入群集，这可能导致分区不平衡散布在群集成员中。使用v1.4，群集将积极地重新平衡负载和重新访问先前不再最佳的位置决策。另一个改进是，分区处理器现在经历了明确的排水和热身阶段，这进一步最大程度地减少了领导力变化期间的破坏 - 这反过来又意味着暂停和更可预测的应用程序。
Restate v1.4 actively rebalances your workload across nodes to ensure an efficient usage of your available resources.
重申v1.4积极地重新平衡您的工作量跨节点，以确保有效地使用您的可用资源。
Cluster-ready out of the box #
套装的群集＃＃
The Replicated loglet provider is a key component at the core of our Bifrost distributed log, and it is now the default in v1.4. When we shipped Restate v1.3, enabling cluster support required explicitly opting into the Replicated loglet as the segmented log backend. In keeping with our “batteries included” philosophy, and thanks in no small part to the design of Bifrost, migration is completely seamless.
复制的Loglet Provider是我们Bifrost分布式日志核心的关键组件，现在是v1.4中的默认值。当我们发货重述V1.3时，启用群集支持需要明确选择作为分段的日志后端中复制的loglet。为了与我们的“包括电池”的哲学保持一致，并在很大程度上要归功于双佛罗斯特的设计，迁移是完全无缝的。
If you have not configured a log provider, Restate will automatically migrate your existing setup to the Replicated loglet implementation, even on single nodes, giving you enhanced performance and a smoother path to distributed deployments. The Local loglet remains available if explicitly configured, and downgrades to v1.3 are safe and supported.
如果您尚未配置日志提供商，那么RESATE将自动将现有设置迁移到复制的Loglet实现，即使在单个节点上，也可以为您提供增强的性能和分布式部署的更平稳的路径。如果已明确配置，则本地loglet仍然可用，并且降级为v1.3是安全且支持的。
We have further streamlined configuration by removing the previously deprecated local metadata backend. The metadata store holds a few tiny yet crucial pieces of information that need to be carefully managed whether in single-node or cluster deployments. The previously deprecated local metadata backend for single-node deployments is removed in v1.4. The default is the replicated metadata server, and nodes will similarly perform an automatic migration on startup if local metadata was previously in use.
我们通过删除先前弃用的本地元数据后端来进一步简化配置。元数据商店拥有一些很小但至关重要的信息，无论是在单节点还是群集部署中，都需要仔细管理。在v1.4中，删除了先前弃用的用于单个节点部署的本地元数据后端。默认值是重复的元数据服务器，如果以前使用了本地元数据，节点将同样在启动上执行自动迁移。
Faster to process your requests #
更快地处理您的请求＃
Whether you are running Restate locally on your development machine or rolling out containers to multi-node clusters, nobody likes to wait. Restate startup latency has improved substantially in v1.4 – the server is now ready to serve requests up to 2.5x faster compared to v1.3.
无论您是在开发机上本地重新启动还是将容器推出到多节点群集中，没人喜欢等待。RESTATE启动延迟在V1.4中有了显着改善 - 与V1.3相比，服务器现在准备好提供2.5倍的请求。
Build with Restate #
使用RENTATE＃构建
As always, the fastest way to get started with Restate is by following the quickstart guide.
与往常一样，开始重述的最快方法是遵循Quickstart指南。
Whether you are still considering Restate for your project, have questions about the upgrade path, or feedback about the new features, we are always keen to hear from you on Discord or Slack.
无论您是否仍在考虑为项目重述，对升级路径有疑问，还是有关新功能的反馈，我们始终渴望在Discord或Slack上收到您的来信。
Restate is open, free, and available at GitHub or at the Restate website. Star the GitHub project if you like what we are doing!
RESATE是开放，免费的，并且可以在GitHub或Restate网站上获得。如果您喜欢我们正在做的事情，请播放Github项目！
Restate is also available as a fully managed service running in our cloud or yours. Try Restate Cloud for free and contact us for more information.
RESATE也可以作为在我们的云或您的云中运行的全面管理服务。尝试免费重述云，并与我们联系以获取更多信息。
