5 ms·
Temporal is such a powerful tool, really don't rollout your own job system using pub/sub, just use Temporal. At first it looks easy to use any pub/sub or DB to
by Thaxll 5y ago
Temporal is such a powerful tool, really don't rollout your own job system using pub/sub, just use Temporal.
At first it looks easy to use any pub/sub or DB to create a job system, but there are so many edge cases, I'm not even talking about scaling etc ... just having a solid job system that properly handle retries, error, durability, timeout etc ...
- djmagee 5y agoIMO, this is the value of Temporal. You certainly can write your own system—but wouldn't you rather focus on writing code that directly addresses the unique value that you or your company offers?
- echelon 5y agoBuild vs buy is hard. Generally you're correct, but then when your tool gets bought out by eg. Splunk (or whomever) and they raise the price 2-5x, you're kind of stuck. Every 3rd party dependency is a complexity you must manage. Every in house system is a complexity you must manage. Nothing is free.
- mkoubaa 5y agoIt's free as in puppy
- swyx 5y agomark my words - temporal will be bigger than Splunk in 5 years. just way bigger TAM.
- echelon 5y agoBest of luck! Love the energy and excitement. :)
- throwoutway 5y agoSplunk’s addressable market is every business right? How is Temporal larger than that? Consumers too?
- swyx 5y agowell theres several ways to answer that. first off characterizing TAM as "every business" is way too broad; up to you how to scope it down but lets say "data analysis for every business". There's not infinite spend for data analysis software. and on the Temporal side, not B2C directly, but serving large B2C. We now can cite Snap as a public customer - every Snapchat story runs through us (and yeah, theres not infinite spend for orchestration either so make of that what you will). and we have bigger users than Snap.
- debuggerpk 5y ago
- suchire 5y agoTemporal is a great system for jobs, workflows, etc. (we use it at my current job), but it isn’t really a replacement for PubSub per se, as there is only one consumer per task
- swyx 5y agoactually true. if you want real pubsub we’re not for that. but we could add the ability for workflows to subscribe to kafka topics in future? no promises on the exact level of abstraction we’ll land on but its definitely been discussed