What is the best way to implement join behaviour for a compound views?
2 Likes
Any thoughts / progress on this?
If Kalix wants to be database-less it may need to provide some way of doing joined / denormalised views across entities within and between services.
One issue I see is that a change to one of the entities (e.g. any master data in a 1-M join) may require an update to multiple “rows” in the view.
We have now released support for “advanced views” with joins and subqueries, see: Implementing Views in Java or Scala :: Kalix Documentation
Note that it is currently not enabled for projects by default though (for scalability/performance reasons).
1 Like
That is fantastic news, thank you. Seems like just what is needed.