Skip to content

Latest commit

 

History

History

eventsourcing

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
aggregate.go
aggregate.go
 
 
state.go
state.go
 
 
state_test.go
state_test.go
 
 
stream.go
stream.go
 
 
stream_test.go
stream_test.go
 
 
types.go
types.go
 
 

README.md

Ergonats Event Sourcing

Ergonats provides a number of building block components for creating an event-sourced application that works seamlessly within an Ergo supervision tree.

Aggregates

An aggregate validates and potentially rejects command requests. If the request passes validation, then the aggregate can emit events to the stream.

An aggregate determines its own internal state by sequentially applying the appropriate events.

To create your own aggregate, all you need to do is create an aggregate struct:

type BankAccountAggregate struct {
	es.Aggregate
}

and then implement the aggregate behavior interface:

InitAggregate(process *AggregateProcess, args ...etf.Term) (AggregateOptions, error)
ApplyEvent(process *AggregateProcess, state AggregateState, event cloudevents.Event) (AggregateState, error)
HandleCommand(process *AggregateProcess, state AggregateState, cmd Command) ([]cloudevents.Event, error)
  • InitAggregate - parameters are passed to the process during the init phase and your aggregate responds with a set of AggregateOptions.
  • ApplyEvent - given an existing state and a cloud event, returns a new state generation
  • HandleCommand - given an existing state and a command request, returns either an error or a list of events to be emitted.