4 ms·
I believe ES has it’s uses in discreet systems doing their thing for you. For me ES makes perfect sense in systems handing a workflow for you. Products like Ze
by jordanbeiber 5y ago
I believe ES has it’s uses in discreet systems doing their thing for you.
For me ES makes perfect sense in systems handing a workflow for you. Products like Zeebe[1] and Ubers Temporal[2] comes to mind.
These systems basically becomes your business transaction log and as such ES is just a great fit.
(I have no idea whether ES is used in temporal though… never looked at the code)
[1] https://github.com/camunda-cloud/zeebe https://github.com/camunda-cloud/zeebe
[2] https://temporal.io/ https://temporal.io/
- swyx 5y agohi! I work at Temporal. ftr our founders left Uber 2 years ago and Temporal is an independent startup (that is very much hiring) now. Short answer is yes, we do, but it's abstracted away so you get the benefits (complete observability, retry/resume from failure) without the downsides (handwriting event sourcing logic and storage). Long answer... it depends what your definition of event sourcing is. We shared some of our internal debate here: https://news.ycombinator.com/item?id=28149159 https://news.ycombinator.com/item?id=28149159 Event sourcing is an impt implementation detail for us, but it is not something we push onto our users. Still they benefit from it anyway. very much agree with your statement. happy to take followup qtns :)