<story><title>Temporal: open-source microservices orchestration platform</title><url>https://temporal.io/</url></story><parent_chain></parent_chain><comment><author>jeffnappi</author><text>Temporal is a company&amp;#x2F;project to watch. The founders know the problem space with as much depth as might be possible. They were responsible for AWS Simple Workflow, then built Cadence Workflow at Uber to solve Uber&amp;#x27;s workflow&amp;#x2F;orchestration issues - and later formed Temporal and forked Cadence to build a company around.&lt;p&gt;I&amp;#x27;m excited for Maxim, Samar and team :)</text></comment>
<story><title>Temporal: open-source microservices orchestration platform</title><url>https://temporal.io/</url></story><parent_chain></parent_chain><comment><author>slotrans</author><text>This is super interesting but I have what feels like a basic&amp;#x2F;dumb question...&lt;p&gt;Let&amp;#x27;s say I have some workflow which executes over a period of days or weeks, and I want to deploy a new version of it. How does that work? What happens to workflow instances that are currently executing?&lt;p&gt;After writing the above I clicked back to the site to see if this was addressed, and found this &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.temporal.io&amp;#x2F;docs&amp;#x2F;java-versioning&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.temporal.io&amp;#x2F;docs&amp;#x2F;java-versioning&lt;/a&gt; and... surely you&amp;#x27;re not serious?</text></comment>