Skip to content

Instantly share code, notes, and snippets.

@Akii
Last active August 29, 2015 14:19
Show Gist options
  • Save Akii/5291b6e468d96c819a48 to your computer and use it in GitHub Desktop.
Save Akii/5291b6e468d96c819a48 to your computer and use it in GitHub Desktop.
Some thoughts about what you could cover in a video about eventstore.
If you have explained some things already, I'm sorry - even though I watched
all your videos, I might oversaw some details or forgot :D
- Stream Names
-> convention that you have aggregate type - identifier
-> what about renaming?
- Projections
-> you held a talk about that, but some short examples would be nice
e. g. how to get the customers that removed an inventory item
3 minutes before the purchase and later bought it
-> Standard projections and what they can used for $et/$ce and so on
- Event migration
-> not the easy kind, the one where you generate new aggregates.
When aggregates are emerging, how do you deal with that? Especially
from a infrastructure point of view, how does the publishing to
remote systems look like (I know very vague, sorry).
- Replaying Events to create Projections (1st NF)
-> Create new streams with projections
-> Insight on how to efficiently create projections for replaying
- Deletions
-> sometimes e. g. law requires you to actually delete data,
any strategies / experiences? How to evaluate the risk?
- Really not important just wondering
Why does the store return 404 on not existing streams but 401 on not existing internal streams? ^.^
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment