This question kinda goes back to the one asked by Felix : "How do you serve the data computed by Samza". If you're interested in that approach (which involves exporting your state to some external serving layer) then you should probably engage on that thread.
The approach you mentions is also in a way pointed out here : http://blog.confluent.io/2015/03/04/turning-the-database-inside-out-with-apache-samza/ . This is mostly about building materialized views in Samza and consuming it via Kafka. My personal opinion: I hope we don't start embedding a data querying / serving layer in the Samza containers - at least not in the production systems. Given that memory is probably the costliest resource to manage, it might pose a problem since we would need a lot of it to provide reasonable (SLA) guarantees for both the streaming and the serving layer. On Tue, Mar 31, 2015 at 5:25 AM, Vladimir Lebedev <w...@fastmail.fm> wrote: > Hey, > > I have samza job with a number of tasks, each of which holds some state in > its embedded store. I want to expose this store for reading to outside > world via some kind of RPC mechanism. What could be the best solution for > this? > > The only solution which comes to my mind is to make my tasks, in addition > to normal processing, to consume request messages with some correlation IDs > on a special request topic, and to put response messages with the same > correlation IDs into special response topic. So it's like RPC-over-Kafka > solution which seems to me suboptimal. > > Any thoughts are welcome! > > -- > Vladimir Lebedev > http://linkedin.com/in/vlebedev > > -- Thanks and regards Chinmay Soman
