Skip to content
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.

Event-sourced processors #100

Closed
krasserm opened this issue Sep 2, 2015 · 8 comments
Closed

Event-sourced processors #100

krasserm opened this issue Sep 2, 2015 · 8 comments
Assignees
Milestone

Comments

@krasserm
Copy link
Contributor

krasserm commented Sep 2, 2015

See event-sourced processors section in documentation.

@krasserm krasserm modified the milestone: 0.4 Sep 14, 2015
@krasserm krasserm added the ready label Sep 18, 2015
@krasserm krasserm added this to the 0.4 milestone Sep 18, 2015
@krasserm krasserm changed the title Event-sourced processors Event-sourced processors for two event logs Oct 28, 2015
@krasserm krasserm self-assigned this Oct 28, 2015
@krasserm krasserm added core and removed core labels Nov 14, 2015
@Tvaroh
Copy link
Contributor

Tvaroh commented Nov 20, 2015

When does this feature is planned to be released roughly? Is there some usable code already available in a branch?

@krasserm
Copy link
Contributor Author

@Tvaroh I just commited an example using Cassandra as query database. This will be in master next week (and available as 0.5-SNAPSHOT in the our repo). An 0.5 release is planned for beginning of next year.

@Tvaroh
Copy link
Contributor

Tvaroh commented Nov 20, 2015

@krasserm awesome, thank you! Does it make sense to just use the Writer in your example to update an external database, e.g. build some graph, but read it directly using some DB-specific API? I mean, read that can only return value of one type cannot express all the cases. Or am I misunderstanding the Writer.read method purpose?

@krasserm
Copy link
Contributor Author

Writer.read is only to initialize the writer (for details, see API docs of EventsourcedWriter). Of course, all other queries should use the DB directly.

@krasserm krasserm changed the title Event-sourced processors for two event logs Event-sourced processors Nov 21, 2015
@krasserm
Copy link
Contributor Author

@Tvaroh Event-sourced writers are now in master (see documentation for details).

@Tvaroh
Copy link
Contributor

Tvaroh commented Nov 21, 2015

@krasserm awesome, will try them out in a near future. Thanks for this awesome work.

Sorry for the unrelated to this discussion question, but what monitoring solution would work better with eventuate?

@krasserm
Copy link
Contributor Author

Thanks for this awesome work.

Thank you for your interest.

what monitoring solution would work better with eventuate

We are currently evaluating that. Follow #110 for updates.

@Tvaroh
Copy link
Contributor

Tvaroh commented Nov 21, 2015

Great, thank you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants