UPDATE: I guess my issue is related to http://apache-ignite-users.70518.x6.nabble.com/Client-requires-DataSource-bean-configuration-copy-td15491.html
My caches are ATOMIC and because I want to externalize my datasource configuration (by making it a Spring bean), I have issues now. So how can I avoid the client from getting confronted with this cache configuration? Should I move my continuous queries to a service in a node and let that service provide a flux (Reactive)? Should I wire the spring context instead of the bean and look it up when needed (client should not need it)? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
