Just stumbled upon this list of DDD resources: Domain-Driven Desire: Further Reading · GitHub
uranther
Feel free to keep it updated with important info/links etc
homanchou
AstonJ
henry-hz
Please, take a look at our new proposal for Commanded CQRS framework:
https://github.com/slashdotdash/commanded/issues/34
3
AndyL
Does anyone know of an event-store that runs in-process? Something like CouchDB or Commanded, but 100% Elixir running in the same process as my application code? I guess I’m looking for the SqLite of event-stores, written in Elixir…
2
slashdotdash
There’s a pending pull request to Commanded that extracts out the storage adapter and provides an additional implementation for Greg Young’s Event Store. With the storage interface now defined as a behaviour you could write an in-memory provider. That would give you a full CQRS/ES library, all in memory and written in pure Elixir.
I do want to implement an in-memory storage provider to use for unit tests. Sorry, I can’t commit to getting it done right now.
1
OvermindDL1
If the information you will store is less than 2gigs then the built-in Mnesia will work. But to say which is best is determined based on what you will be storing, how it will be stored, and how it will be looked up.
1
AndyL
@slashdotdash and @OvermindDL1 - thanks for your responses.
Another more general question - I’m trying to figure out a strategy for dealing with Code change in my Event Sourced app. Can you point me at a a good reference or talk that explains different strategies for managing code changes, especially when you need to change the format of the messages stored in the Event Store?
1
OvermindDL1
I version my messages and just run them through converters.
event = %EventMsg{vsn: 3, blah: :blorp} # Except you can make the 'current' `vsn` the default value too
2