Adam tip叩k discusses using event sourcing (ES) for a new project in 2018. He considers different ES libraries and tools, noting that Broadway has poor documentation and Prooph will be deprecated. tip叩k outlines future plans to develop an Event Store client for asynchronous TCP connections and one for HTTP. He concludes by outlining some key aspects of thinking in ES, such as creating event-sourced entities and handling periodic events.
1 of 14
Download to read offline
More Related Content
Techforce #5 es in 2018
1. Adam tip叩k | @new_POPE | rekurzia.sk
EEEEEEES in 2018
2. new project, event here, event there, cqrs, es, booom ...
Easy, I have a solution. ES
3. my next steps ...
Library ?!
https://sketcher.startitup.sk/najkrajsie-kniznice-europy-ktore-by-si-mal-navstivit/trinity-college-library-dublin-1732/
4. let the tournament begun
https://media.giphy.com/media/7d7lKk2nH5RJu/giphy-downsized.gif
5. after a few rounds
study, study study ...
https://www.extra.cz/tady-se-vladimir-iljic-lenin-chystal-na-smrt-jsou-fotky-ktere-vydaji-za-miliony-slov
7. real tools
Broadway (https://github.com/broadway/broadway)
Poor documentation
Prooph (https://github.com/prooph)
This library will receive support until December 31, 2019 and will then be deprecated.
8. future
Event Store Client for async TCP connections
Event Store HTTP Client for HTTP connections
11. Thinking in ES
1. Event sourced entities
a. Creating entities, data sending
2. Event dispatching
a. Implementation
3. Sync vs. Async events
a. Development vs. production vs. debugging
4. Events
a. Periodical events (birthday -> age)
12. Thats all folks. Good luck.
Adam tip叩k | @new_POPE | rekurzia.sk