Demystifying Event Processing in Axon Framework

In Axon applications, Event Handlers define the business logic to be performed when an Event is received. Event Processors are the components that take care of the technical aspects of that processing. They come in roughly two forms: Subscribing and Tracking. The Subscribing Event Processors subscribe themselves to a source of Events and are invoked by the thread managed by the publishing mechanism. Tracking Event Processors, on the other hand, pull their messages from a source using a thread that manages itself.

Transcript

1. Demystifying Event Processing in Axon Framework @MilanSavic14
2. Milan Savić Software Engineer @ AxonIQ milan@axoniq.io @MilanSavic14 m1l4n54v1c @MilanSavic14
3. Axon @MilanSavic14
4. Subscribing Event Processor @MilanSavic14
5. Live Demo @MilanSavic14
6. Tracking Event Processor @MilanSavic14
7. Processing Loop @MilanSavic14
8. Live Demo @MilanSavic14
9. Parallel Processing @MilanSavic14
10. Live Demo @MilanSavic14
11. Distributed Processing @MilanSavic14
12. Live Demo @MilanSavic14
13. Summary • Subscribing Processing gives you ACID • Tracking Processing enables loose coupling • Configure number of threads to increase vertical scalability • Spread Tracking Processor load to several nodes to increase horizontal scalability • Axon Server gives you possibility to automatically spread the load @MilanSavic14
14. Resources • https://github.com/m1l4n54v1c/event-processing • https://axoniq.io/blog-overview/tracking-event-processors • https://axoniq.io/blog-overview/cqrs-replay-performance- tuning @MilanSavic14
15. Thank you! • Q&A @MilanSavic14