- With all the focus on scalability and complex microservices architecture Temporal may be overkill.
This is what most users care about. But Temporal programming is a good fit for some monolithic applications that require reliability as well.
- I don’t have realtime (e.g. gaming) low-latency requirements. Temporal might be at the core of entire architecture.
Good fit here.
- But with that do I have enough control of how data is persisted, or maybe I don’t need to care about that any more.
It depends on the data. Temporal persists data that is related to the lifecycle of objects it manages. It is not built to store historical data for example.
- How would I go about implementing the read-side of CQRS using Temporal (Kafka suggested elsewhere probably overkill too)?
Use query workflow feature of Temporal.
- I saw that Temporal can be imported / embedded. How involved is that, and will you continue to support that option?
We want to support extending Temporal without the need to fork the main repository. So we certainly going to support this option.
- Would it be complex to replace Elasticsearch with something else (thinking of lieu [1] )?
It would be a pretty significant project. I think we are going to add support for custom attributes on top of SQL databases sooner.