Temporal V1 Release

6 posts · Jul 2020 – Sep 2020

What this trail covers

Temporal V1 marks the production-ready release of the Temporal platform, signifying a commitment to backward compatibility for publicly facing APIs. This release includes improvements to shard ID hashing, which may cause temporary resource usage increases during in-place upgrades. Features like Archival, Cross Data Center Replication, Batch Operations, Dynamic Config, and dynamic management of searchable attributes with Elasticsearch are designated as 'experimental' and will undergo further validation.

All Temporal trails

Sep 2020Temporal V1 AnnouncementThis post announces the official production release of Temporal V1, signifying a commitment to backward compatibility for publicly facing APIs. It details improvements to shard ID hashing, which may cause temporary resource usage increases during in-place upgrades. Features designated as 'experimental' include Archival, Cross Data Center Replication, Batch Operations, Dynamic Config, and dynamic management of searchable attributes with Elasticsearch.
Sep 2020Temporal Transparency Update #8This post announces that Temporal has reached code completion for its V1 stabilization effort, with all tests for V1 now running in the pipeline. Several parts of the system have already been stabilized, and the number of bugs found is decreasing. The post also lists Archival, Cross Data Center Replication, Batch Operations, Dynamic Config, and dynamic management of searchable attributes with Elasticsearch as experimental features for the V1 release, with plans to productionize them post-launch.
Sep 2020Temporal Transparency Update #7This post details the stabilization progress for Temporal V1, focusing on deployment infrastructure improvements (dedicated Cassandra cluster, isolated Cassandra nodes from Temporal server for perf testing), completion of non-failure bench scenarios, initial work on failure scenarios (integration with Gremlin pending), validation of component failure/resumption tests, and ongoing development of backlog scenarios. It highlights a decreasing trend in newly discovered bugs, indicating successful stabilization efforts.
Aug 2020Temporal Transparency Update #5This post details the final stages of code completion for the JavaSDK, including a significant refactor and the submission of a PR for review. It also announces the team's shift in focus to stabilization efforts for Temporal V1, outlining key areas of investment: automated deployment infrastructure using Concourse for CI/CD pipelines, rigorous scale testing to ensure graceful load handling, and comprehensive failure testing to guarantee system resilience and workflow progress during failures. The post reiterates the commitment to backwards compatibility and schema compatibility, while strongly advising against using the current release in production due to the ongoing stabilization process.
Jul 2020Temporal Transparency Update #4This post announces that Temporal server and GoSDK are code complete for V1, with no more breaking API/code changes for these components. JavaSDK changes are delayed to the following week. The focus has shifted entirely to stabilization, with the goal of ensuring reliability over velocity. Production usage will be encouraged only after V1 stability is confirmed. Breaking schema changes are not expected post-V1 release. A changelog for changes since Cadence fork is provided.
Advertisement