[swyx]

ctrl+f "state machine" on this page :) but yeah this is a very good perspective on temporal. we should talk, if you're interested in helping us tell our story better.

i'm actually interested in a longer form "Temporal vs K8s" comparison - can make a case for Temporal atop k8s, or Temporal replacing k8s (already had a couple customers talk to us about this). It's a nuanced story to tell and I'm not sure if it has a conclusion.

[sunny--tech]

The company I work at runs a HA setup of Temporal on K8s, so Temporal atop k8s is a great recipe. I'd be curious to hear the reasoning for Temporal replacing K8s (or do you just mean replacing a piece of k8s?) Seeing as how as reconciliation is just a tool it uses for it's container orchestration, not sure Temporal would replace that but an interesting idea nonetheless.

[swyx]

yeah tbh this idea came from our users so i cant really speak to it but they really mean replacing k8s. this one for example is a large Jamstack/CI/CD provider with very spiky workloads. To them, k8s, ecs, fargate, etc are all too slow and declarative, they need to spin up + spin down (major motivation, for cost) infra way faster and do more custom stuff so they turn to us. i dont claim to fully understand it but does that give a hint?