All, We are in a situation where we have to query data over several caches. As we all know, joins are a nightmare in a distributed system and I know there are other means like denormalisation, but it is not sufficient anymore in some cases we have and we need the joins.
We mainly work in an OLTP context, where queries are known in advance (ie dev time) and inpsired by following blog of several years ago, I was wondering if the concept of “materialized views” could make it into Apache Ignite. (https://www.confluent.io/blog/turning-the-database-inside-out-with-apache-samza/ ) It would work as follows: * A query must register itself in Ignite at startup time (eg. via configuration) or during run time (eg. API call) * The registered query is parsed and a new “view” cache is created which will ‘cache’ the resultset of the query (could take a while, but intermediate status can be “warming up” and “hot” when ready) * All caches involved in the joins are now monitored for CUD operations and relevant data is stored in the new “view” cache so the view gets updated in real time * All operations must be ACID compliant * The view is queried via a very trivial select statement Would that be feasible as a new feature? Regards, Sven [cid:image001.png@01D3007B.4D007790] SVEN BEAUPREZ L e a d A r c h i t e c t De Kleetlaan 5, B-1831 Diegem www.theglue.com<http://www.theglue.com/>
