5 ms·
For whatever it's worth, I feel like this might be pretty interesting, and I maybe even have a need for something like it, but needing to spin up an unfamiliar
by doctor_eval 4y ago
For whatever it's worth, I feel like this might be pretty interesting, and I maybe even have a need for something like it, but needing to spin up an unfamiliar database (elastic) is pretty much a show stopper for me.
- qlong-seattle 4y agoYou don't have to run elastic. Cadence/Temporal let you run only with database for majority of the feature/power. ElasticSearch is only for supporting the searching functionality(advanced visibility). https://docs.temporal.io/visibility https://docs.temporal.io/visibility https://cadenceworkflow.io/docs/concepts/search-workflows/ https://cadenceworkflow.io/docs/concepts/search-workflows/ Same as in iWF, you can use a Temporal service without advanced visibility. E.g. this doc is showing how to run with Temporalite which doesn't have advanced visibility with it. https://github.com/indeedeng/iwf/blob/main/CONTRIBUTING.md#option-2-run-with-your-own-temporal-service https://github.com/indeedeng/iwf/blob/main/CONTRIBUTING.md#o... Again, you still have 90% power and the only thing missing is searching for workflows using "search attributes". You can still store data in search attributes but they are just not searchable. And later, you can migrate to a Cadence/Temporal service that has advanced visibility enabled.
- doctor_eval 4y agoOk thank you for that. This is a bit above my pay grade right now but I will see if I can wrap my head around it in the coming days.