Repository navigation
Support multiple event stores - #55
Merged
Merged
Conversation
…ify event names different from event module name by use'ing EventName 'custom-event-name'
…ate.aggregate_version from last received RecordedEvent.event_id
…e to update aggregate_version
…a read did not reach end of stream and the number of read events are less than given count
Initial in-memory default event store adapter. Set default adapter to `Commanded.EventStore.Adapters.InMemory`
Bump version to v0.10.0
They will be moved into their own projects.
Use latest Erlang and Elixir versions.
Define module name type provider as default implementation. So
`%An.Event{}` module is mapped to the type string "Elixir.An.Event".
Adapter should configure its own supervision tree using the mix application settings.
This was referenced May 14, 2017
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extract event store integration to a behaviour (
Commanded.EventStore). This defines the contract to be implemented by an event store adapter. It allows additional event store databases to be used with Commanded.By default, a
GenServerin-memory event store adapter is used. This should only be used for testing as there is no persistence.The existing PostgreSQL-based eventstore integration has been extracted as a separate package: commanded_eventstore_adapter.
There is now a new adapter for Greg Young's Event Store using the Extreme library, available as package: commanded_extreme_adapter.
You must install the required event store adapter package and update your environment configuration to specify the
:event_store_adaptermodule. See the README for details.Thanks to @sharksdontfly for taking this feature on and getting the multiple event store adapters implemented.