innoave / eventmill Goto Github PK

Thanks for the great work so far: loving the clean and clear API!

I'm trying to find out the bouds of this library: to know, if I choose this as basis, what I'll have to implement myself outside of this lib.

Right now, there is only a InMemoryStore implementation for events; which is great for a PoC and maybe some use-cases, but I need persistent storage. Anything would do for now: from JsonFilesStorage to PostgresStorage to GetEventSourcedStorage.

Is this planned? Or is this deliberately left out of the library and left for the implementer?

I'm trying to find out the bounds of this library: to know, if I choose this as basis, what I'll have to implement myself outside of this lib.

Right now, there is no projection in place. Nor do I see any mention of other event-processors (WorkFlows, Reactors, etc) in the code or the readme.

I'm currently in need of an event-source system that projects data into files (KML/GML/XML) and into a database (PostGIS).

Is this planned as part of this library? Or is this deliberately left out of the library and left for the implementer?

If the latter, it might be a good idea to outline some additional requirements (or a sample implementation), so that an implementer has something stable-ish to work against. E.g. a processor might need to implement mutex-locks and/or cursors; whose implementation depends greatly on details such as the ID of-, ordering of-, delivery of- events.