Open Source Commitment and Lock-In Concerns

Building for Reliability: Durable Execution & Insights from Temporal's Report - Preeti Somal

Topic 9 of 11

Published Oct 6, 2025 · Clip 51:24–54:09 (2:46)

Preeti addresses vendor lock-in concerns by pointing to Temporal's open source commitment: developers can run their code on the open source server in their own infrastructure or bring it to Temporal Cloud without code changes, with a guaranteed code compatibility between cloud and open source. She acknowledges the programming model itself is sticky—switching models requires code changes—but developers don't have to rely on Temporal the company since the server is open source. The host draws a parallel to Apache Beam's multi-runner portability model.