I'm talking about DI in the constructor parameter sense here. I've gone through some of the documentation, but one thing that's not clear to me is the expected model of how to efficiently execute many instances of 'similar' graphs.
To elaborate on what I mean, I'm working on a PoC where I'm creating a main flow graph to manage data fetching, with the 'shape' of the graphs being mainly the same, except for an inlet which can be either capped with an empty source, or with a source which is essentially a recursive copy of the main one (with potentially many levels). While the shape is regular, many nodes are parameterized with various interfaces which control how to generate data requests, how to interpret responses, how to handle errors, etc. Right now my experimental code is just creating the graphs and passing the interface instances into their constructors, so each graph is essentially single use. This feels possibly inefficient, to create the entire graph, bottom up, for each query. Code-wise I can refactor everything into nice functions, but maybe I'd be making the framework waste time re-optimizing identical graphs repeatedly. I might be overthinking, but I'm curious about any suggestions on how to organize things here. Cheers, Matthew Wozniczka -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
