Getting started with event sourcing in Laravel

  Рет қаралды 15,170

Freek Van der Herten

Freek Van der Herten

Күн бұрын

Пікірлер: 13
@sethcenterbar
@sethcenterbar 4 жыл бұрын
This is BY FAR the best demonstration of event sourcing on the internet. Thank you so much, I've been researching for two weeks trying to understand this better.
@КонстантинС-ж1ы
@КонстантинС-ж1ы 5 жыл бұрын
Very useful hour of my life. Thank you.
@streakifyapp
@streakifyapp 4 жыл бұрын
Great introduction! Very well explained and concise, many thanks.
@ravenbergdev
@ravenbergdev 5 жыл бұрын
This replay events command is amazing
@jitendra8030
@jitendra8030 4 жыл бұрын
Thanks a lot for this effort. I finally understood event sourcing.
@niided
@niided 4 жыл бұрын
Great! I have a better understanding now. Thank you.
@tomatomov9061
@tomatomov9061 2 жыл бұрын
What I didnt understand is how the events are stored in DB ? Didn't see any insert query. Is stored_events some default table that comes with some event package in laravel ?
@kenjohnsiosan9707
@kenjohnsiosan9707 4 жыл бұрын
can I apply this approach to a loan management application with financial reporting? please advise. thank you
@tomatomov9061
@tomatomov9061 2 жыл бұрын
Another question. Why the Aggregate Loan example on min 30, cant be made with simple if statement instead of 100 classes, interfaces, events and such ? if ( ($currentAmoun + $currentWithdraw) > 5000 ) { if ({some_query_to_retrieve_the_limitHit_event_counts} === 3) { //Insert "LoanProposal" event in the event log table } //Insert "LimitHit" event in the event log table } Of course it's just imply example. It could be made with methods from some class or similar. But what is the benefits from doing this with all the interfaces. events. projectors, reactors and etc. ? I am not trying to make fun or something. Really can't explain it to myself.
@Paltibenlaish
@Paltibenlaish 2 жыл бұрын
why not create an accounts_history table separately? and save the history in the traditional app
@orbitory7936
@orbitory7936 4 жыл бұрын
So what happens in case stored events table has lots of rows for an account, over the years can be hundred of thousands per account so you have to do a lot of data calculation? Maybe more logic can be added so only last N rows are used to recalculate the balance. Isn't it better to use a counter field in the account table to trigger the sending of the loan email for this case specifically?
@mabdullahsari
@mabdullahsari 5 жыл бұрын
Would it be fair to say that this is Redux for the backend (kind of)
5 жыл бұрын
I think so. It's also very similar to store your api requests in a list and process it whenever you want.
Real Man relocate to Remote Controlled Car 👨🏻➡️🚙🕹️ #builderc
00:24
УДИВИЛ ВСЕХ СВОИМ УХОДОМ!😳 #shorts
00:49
HARD_MMA
Рет қаралды 2,6 МЛН
كم بصير عمركم عام ٢٠٢٥😍 #shorts #hasanandnour
00:27
hasan and nour shorts
Рет қаралды 10 МЛН
Getting started with Domain Oriented Laravel
7:28
Freek Van der Herten
Рет қаралды 15 М.
A pragmatic introduction to Event Sourcing.
59:11
Frank de Jonge
Рет қаралды 5 М.
Launching Event Sourcing in Laravel
56:41
Freek Van der Herten
Рет қаралды 3 М.
Building microservices with event sourcing and CQRS
1:24:33
SpringDeveloper
Рет қаралды 112 М.
Keynote: Event sourcing - Greg Young - DPC2016
54:43
Ibuildings Dutch PHP Conference
Рет қаралды 23 М.
Freek Van der Herten - Simplification Tips and Tricks
31:18
StreamACon Streaming Conferences
Рет қаралды 18 М.
Laravel Worldwide Meetup: Termwind and Inertia
1:52:34
Freek Van der Herten
Рет қаралды 3,1 М.
Scaling Event Sourcing for Netflix Downloads
50:50
InfoQ
Рет қаралды 36 М.
Introducing spatie/laravel-data
21:17
Freek Van der Herten
Рет қаралды 10 М.
Event Sourcing in Laravel with EventSauce by Dries Vints
31:50
Real Man relocate to Remote Controlled Car 👨🏻➡️🚙🕹️ #builderc
00:24