I don't know. library-eventsourcing was contributed from a downstream project, and I haven't worked with it. And perhaps it is not in scope of what you want to do... See Martin Fowler's and Greg Young's definition of Event Sourcing.
For general event streaming, we are planning to have more explicit support in 3.x, similar to the persistence support. But it is currently unclear what core features and SPI is needed for this, and use cases are most welcome. There are many ways you could integrate a Kafka consumer or producer into Zest. My guess would be that a service listens to Kafka system events and the service creates/destroys Zest resources when needed. Note that entities will not be able to be Kafka listeners, as you will not be able to maintain a valid UnitOfWork while waiting. Hope that helps On Apr 20, 2016 13:06, "zhuangmz08" <[email protected]> wrote: > Hi, > Is there any mechanism to use event streaming / data feeding with zest. > I'd like something subscribe-publishing like Apache Kafka. I have a data > feed server and a set of data feed subscribers. > Each time a feed client subscribe a new topic (a new Value/Entity > Composite type), the data feed server will add this subscribe into its > listener list. As soon as the topic event takes place, it will notify all > the related listeners. > 1. Is event sourcing able to subscribe/unsubscribe listeners on demand? > 1. Does event sourcing have to store every event? I don't need to persist > every event. In other words, one of the listeners will handle event > storage, other listeners will pay more attention on real-time event stream > handling. > > > Thanks a lot.
