// Once we have electric, we then establish the data change
// notification subscription, comparing the tablenames used by the
// query with the changed tablenames in the data change notification
// to determine whether to re-query or not.
//
// If we do need to re-query, then we use the saved function to reuse the query
So it re-runs queries on all updates in tables from the query.
Check data sheets for any 3d printing filament, Young’s modulus is the main characteristic in them and that's how you can reason about filament abilities.
Based on what I read it's very similar to Kafka Streams + batteries ([semi]automatic workload orchestration, reactive queries, higher-level/slicker/"smarter" API (?))
Could you please compare Rama with Kafka Streams, especially from the point of view, if I would try to reimplement Rama API on top of Kafka Streams? What fundamental difficulties I'd face?
So it re-runs queries on all updates in tables from the query.