2 ms·
Good question. I operate a pretty big Temporal deployment at work (~3.45 billion actions per month), and also have the dubious distinction of being one of the o
by iand675 21d ago
Good question. I operate a pretty big Temporal deployment at work (~3.45 billion actions per month), and also have the dubious distinction of being one of the only community SDK (Haskell) implementors for Temporal. So I have a pretty good sense of rough edges and my own areas of dissatisfaction, and also what I'd want out of a next generation system.
So, hello frenemies, I suppose :)
- hypervs 21d agoWhich rough edges pushed you toward the same mechanism - history growth, replay latency, determinism/versioning, worker ops, or the programming model? Happy to compare notes.
- elendilm 21d agoDefinitely friends, not frenemies. I have nothing but genuine respect for builders out there solving hard infrastructure problems. We are primarily focused on our Feature Architecture. Durable execution is only for command features, requires tight coupling with our architecture, and is not a standalone dedicated tool like Temporal. Open to further discussion on both of our work's trajectories rather than digress here.