Event Sourcing is seemingly constantly being confused with Event Driven Architecture. In this video I'm going through a popular blog post that explains various points that are very valid, however, they are conflating Event Sourcing with Event Driven Architecture. Event Sourcing is about using events as the state. Event Driven Architecture is about using events to communicate between service boundaries.
🔗 EventStoreDB
[ Ссылка ]
🔔 Subscribe: [ Ссылка ]
💥 Join this channel to get access to source code & demos!
[ Ссылка ]
🔥 Don't have the JOIN button? Support me on Patreon!
[ Ссылка ]
Oskar Dudycz: Event Streaming is not Event Sourcing!
[ Ссылка ]
Original Blog Post
[ Ссылка ]
📝 Blog: [ Ссылка ]
👋 Twitter: [ Ссылка ]
✨ LinkedIn: [ Ссылка ]
📧 Weekly Updates: [ Ссылка ]
0:00 Intro
0:58 Event Sourcing is an anti-pattern
5:15 Upstart Costs are Large
6:38 Event Sourcing needs the UI side to play along
7:51 Building two different systems along side each other
9:48 Audit log will often have fidelity problems
10:51 Dealing with materialization lag
#eventsourcing #eventdrivenarchitecture #softwarearchitecture
Don't Let the Internet Dupe You, that's NOT Event Sourcing
Теги
Event Sourcingcqrsmicroserviceskafkaevent driven architecturemicroservice architectureevent sourcing microservicesevent sourcing vs event drivenevent sourcing cqrsevent sourcing patternevent sourcing greg youngevent sourcing architectureevent sourcing awsevent sourcing kafkaevent sourcing pattern microservicesevent sourcing laravelevent sourcing martin fowlerevent sourcing microservices cevent sourcing archetectureEvent sourcing projections